caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: David MENTRE <dmentre@linux-france.org>
To: Cezary Kaliszyk <cek@zodiac.mimuw.edu.pl>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Intelligent handling of dependencies in complex ocaml projects
Date: Wed, 14 Apr 2004 14:56:09 +0200	[thread overview]
Message-ID: <87ad1ewweu.fsf@linux-france.org> (raw)
In-Reply-To: <20040414123026.GA25996@zodiac.mimuw.edu.pl> (Cezary Kaliszyk's message of "Wed, 14 Apr 2004 14:30:26 +0200")

Hello Cezary,

Cezary Kaliszyk <cek@zodiac.mimuw.edu.pl> writes:

> Ocamldep is insufficient becouse it requires providing all
> source files (from all directories) in command line.
>
> Different subprojects depend on different external libraries. These 
> libraries may require different linkingflags. Some of them are
> contradictory. So I can't call ocamldep like 
>   ocamldep `find . -name "*.ml"`
> because it requires all those flags together.

Have you considered calling several times ocamldep (from your root
directory), each time with the specific options, and then using the
"-include" directive of make to import them in the main Makefile?

I'm using a similar approach to generate dependencies in two successive
phases.

I hope it helps,
Yours,
david
-- 
 David Mentré <dmentre@linux-france.org>

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  reply	other threads:[~2004-04-14 12:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-14 12:30 Cezary Kaliszyk
2004-04-14 12:56 ` David MENTRE [this message]
2004-04-14 15:18 ` Richard Jones
2004-04-14 15:36   ` Kenneth Knowles
2004-04-15  7:46     ` David MENTRE

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=87ad1ewweu.fsf@linux-france.org \
    --to=dmentre@linux-france.org \
    --cc=caml-list@inria.fr \
    --cc=cek@zodiac.mimuw.edu.pl \
    /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;
as well as URLs for NNTP newsgroup(s).