From: Xavier Leroy <xleroy@pauillac.inria.fr>
To: e-posse@argos.uniandes.edu.co
Cc: caml-list@pauillac.inria.fr
Subject: Re: ocamldep
Date: Thu, 18 Jul 1996 15:33:42 +0200 (MET DST) [thread overview]
Message-ID: <199607181333.PAA14029@pauillac.inria.fr> (raw)
In-Reply-To: <31EC2675.283@argos.uniandes.edu.co> from "Ernesto Posse" at Jul 16, 96 06:32:05 pm
> Hello everybody. I have been having a little trouble with the Dependency
> Generator ocamldep that comes in the Windows 95 version 1.01 of O'Caml.
> The reference manual says that the typical use of ocamldep should be
> something like this:
>
> ocamldep *.mli *.ml > .depend
>
> The problem is that ocamldep doesn't seem to recognize the *.mli and
> *.ml arguments
Well, the Objective Caml sources come from a Unix background, where
wildcards (*.ml) are expanded by the command shell and the commands
receive an already-expanded argument list. One day I may add
command-line expansion in the Objective Caml start-up code, but don't
hold your breath.
> and I have to list explicitly all of my project files but
> I get a "line too long" error from the line command interpreter. (a
> MS-DOS window).
I thought Win32 finally raised the length limit on the command line to
some reasonable value like 4k. At any rate, you can always split the
call to ocamldep thus:
ocamldep [some files] > .depend
ocamldep [more files] >> .depend
...
Also, a "for" loop may work, for instance
for %i in (*.ml) do ocamldep %i >> .depend
(that's probably the wrong syntax, but you get the idea).
- Xavier Leroy
next prev parent reply other threads:[~1996-07-18 18:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-07-16 23:32 ocamldep Ernesto Posse
1996-07-17 18:21 ` ocamldep Georg Bauer
1996-07-18 13:33 ` Xavier Leroy [this message]
1996-07-19 1:27 ` ocamldep Ian T Zimmerman
1996-07-20 14:48 ` ocamldep Georg Bauer
1996-07-18 21:21 ocamldep Doug Currie, Flavors Technology, Inc.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=199607181333.PAA14029@pauillac.inria.fr \
--to=xleroy@pauillac.inria.fr \
--cc=caml-list@pauillac.inria.fr \
--cc=e-posse@argos.uniandes.edu.co \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox