caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: <sylvain.le-gall@polytechnique.org>
To: Nicolas Cannasse <warplayer@free.fr>
Cc: David Brown <caml-list@davidb.org>,
	Martin Jambon <martin_jambon@emailuser.net>,
	caml-list@inria.fr
Subject: Re: [Caml-list] Building large and portable projects
Date: Fri, 21 Nov 2003 07:49:50 +0100	[thread overview]
Message-ID: <20031121064950.GA836@gallu.homelinux.org> (raw)
In-Reply-To: <008301c3aff3$1030e760$0274a8c0@PWARP>

On Fri, Nov 21, 2003 at 02:48:17PM +0900, Nicolas Cannasse wrote:
> > > What is the difference with OCamake ?
> > > http://tech.motion-twin.com/ocamake/
> >
> > There are a lot of things that OCamake can't do.  What would be very
> > nice would be a tool that makes it easy to build simple Ocaml programs,
> > but also lets me, reasonably easily, manage directory trees, C bindings,
> > C libraries, programs build with special, strange programs, etc...
> >
> > There are several packages in the scons approach that seem like good
> > ideas, but they all make very heavy use of the scripting languages they
> > are written in.
> >
> > I still haven't found anything nicer than gnatmake, the builder for Gnu
> > Ada.  A common compilation line:
> >
> >   gnatmake mainmodule
> >
> > Builds mainmodule.adb, as well as everything it depends on.  You can set
> > a path to search for parts.  This would work for ocaml, if a program had
> > a single module that brought in everything necessary via dependencies.
> 
> I agree such a thing would be very useful.
> 
> The first problem I see is that right now ocamldep is only giving you the
> dependencies between files that are listed in the ocamldep command. That
> means that you already need to know all the files before generating the
> dependencies between them.
> 
> The other problem is that to much of the "special programs build" are
> relying on OS tools that are sometimes not stricly compatible. The solution
> to this is to rewrite all the tools in pure ocaml ( or with a small portable
> C binding ) to give the "makefile" writter an API of portable commands. It
> looks like this is the goal of Sylvain, and that would be really something
> nice.
> 
> About OCamake : yes right know it only supports compilation of
> ml/mli/mll/mly files in a standard way, but it is now mature and is actually
> handling a lot of cases such as projects with multiple files paths and a
> best effort dependency resolver (although based on ocamldep output). Adding
> the auto building of C stubs could be done but this kind of tool need a lot
> of time in order to fix correctly all the small issues.
> 
> Nicolas Cannasse

Hello,

Well, i will maybe stole your code ;->

My aims is to make something more Makefile like ( ie you will have the
ability to add rules ). Off course, my first goal is to compile ml file.
So there will be less features than Makefile.

On the other hand the aim will be to have a self contained tools ( ie
when you write a makefile you use rm, cp, touch... here the aims will be
to have it in ocaml ). So you could build on every platform which
support ocaml.

Your makefile will be written in ocaml !

Regard
Sylvain LE GALL
> 

-------------------
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


  parent reply	other threads:[~2003-11-21  6:50 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 18:47 Martin Jambon
2003-11-20 19:56 ` sylvain.le-gall
2003-11-21  1:45   ` Nicolas Cannasse
2003-11-21  5:25     ` David Brown
2003-11-21  5:48       ` Nicolas Cannasse
2003-11-21  6:45         ` David Brown
2003-11-21  6:49         ` sylvain.le-gall [this message]
2003-11-21 16:12           ` skaller
2003-11-21 17:53             ` Eric Dahlman
2003-11-22 14:45               ` skaller
2003-11-21 19:04             ` sylvain.le-gall
2003-11-22 14:34               ` skaller
2003-11-22 18:50                 ` sylvain.le-gall
2003-11-22 14:32             ` Martin Berger
2003-11-22 14:55               ` skaller
2003-11-22 17:08             ` David Brown
2003-11-22 16:48               ` skaller
2003-11-23  3:25               ` Nicolas Cannasse
2003-11-23  4:29                 ` David Brown
2003-11-23 17:21                 ` skaller
2003-11-22 17:13             ` David Brown
2003-11-24 18:02             ` Ken Rose
2003-11-24 19:04               ` Christian Lindig
2003-11-21 16:32           ` Martin Jambon
2003-11-21 18:57             ` sylvain.le-gall
2003-11-21  9:14       ` Christian Lindig
2003-11-21  9:28 ` Richard Jones
2003-11-21 15:35 ` skaller
2003-11-21 17:05 ` Jason Hickey
2003-11-21 18:55   ` sylvain.le-gall
2003-11-21 19:30     ` [Caml-list] Omake [Was: Building large and portable projects] Aleksey Nogin
2003-11-21 20:39       ` Damien
2003-11-22  3:30         ` Aleksey Nogin
2003-11-21 23:48       ` sylvain.le-gall
2003-11-22  1:32         ` Nicolas Cannasse
2003-11-22  3:51         ` Aleksey Nogin
2003-11-28 16:29   ` [Caml-list] Building large and portable projects David Brown

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=20031121064950.GA836@gallu.homelinux.org \
    --to=sylvain.le-gall@polytechnique.org \
    --cc=caml-list@davidb.org \
    --cc=caml-list@inria.fr \
    --cc=martin_jambon@emailuser.net \
    --cc=warplayer@free.fr \
    /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).