>>>>> "NC" == Nicolas Cannasse <warplayer@free.fr> writes:

    >> The problem is that every package has a different build system,
    >> configuration system (Makefile targets), installation
    >> directories, etc. Of course it is "easy" to package them : just
    >> issue the right (Makefile or whatever) commands, set the right
    >> Makefile variables, etc. The problem is that you have to spend
    >> some time figuring out these commands. Ideally, it should be as
    >> simple as :
    >> 
    >> perl Makefile.Pl or python ./setup.py build
    >> 
    >> One more point is that ocaml is multi-platform : so this build
    >> system should be able to run on unix, Windows, MacOS. Packages
    >> that wraps C libraries will probably be platform-specific but
    >> it think it would be nice if pure ocaml programs could be built
    >> the same way on every platform supported by ocaml.

    NC> Will I need to install wonderful programming langages such as
    NC> perl or python on my Windows box ? Without any flames, why are
    NC> always unix users wants to make things so complicated ? :) I
    NC> will much more prefer something like :

Have you tried OCamlMakefile?  I gotta say -- I do a lot of weird
stuff with Caml (preprocessing with a custom-written #define
processor, amongst other weird stuff), and it's worked more-or-less
like a charm.

Indeed, I'd like to encourage others to use this puppy.  It *works*.

A combination of OCamlMakefile, and "findlib" (Thanks, Gerd!!!!)
really, really, really (did I mention really?) works to eliminate
almost all my building and packaging hassles.

I suspect that some sort of Makefile-generating facility, written in
Caml (of course), combined with OcamlMakefile, and producing findlib
modules, would be *near-ideal*.

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