From: r.3@libertysurf.fr
To: caml-list@inria.fr
Subject: Re: [Caml-list] One build system to rule them all?
Date: Fri, 19 Sep 2014 11:14:23 +0200 (CEST) [thread overview]
Message-ID: <1839435586.73559263.1411118063407.JavaMail.root@zimbra27-e5.priv.proxad.net> (raw)
In-Reply-To: <CAN6ygO=P_QTa6Wk0=Wx=0XLwhGOP=16eGaGiacA5N60nRjApDQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Hello,
Some time ago I set up a cross tool chain from linux to windows. The project was using lablgtk2, camlimages, xml-light, lablgl and cairo. None of these packages were ready for cross-compilation, and I had to patch them.
My experience :
Makefile (small ones) : was ok
oasis (for my own packages) : was not possible to cross-compile
ocamlbuild through Makefiles (for my own packages) : ok
autotools + ocaml-autoconf + Makefiles (lablgtk2, cairo) : my preferred
oMake (camlimages) : seemed obscure to me, and did not succeeded in patching it. In the end, I reverted to a previous version of camlimages using autotools + ocaml-autoconf + Makefiles
In the end, to my point of view, I found ocamlbuild to be nice for small to medium ocaml projects, though documentation was bad. Then, when C sources were required with cross compilation, or for bigger projects, I found autotools to be nice.
Finally, I also tend to think that the best tool is the one used by most people :-)
Just to get fun, I designed two polls :
"best tool" :
http://vote.pollcode.com/55577581#sthash.7DIWIfiP.dpuf http://vote.pollcode.com/55577581
"most used tool" :
http://vote.pollcode.com/114772714
William
http://vote.pollcode.com/55577581#sthash.7DIWIfiP.dpuf
[-- Attachment #2: Type: text/html, Size: 2493 bytes --]
prev parent reply other threads:[~2014-09-19 9:14 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 12:49 Yotam Barnoy
2014-09-10 13:00 ` Simon Cruanes
2014-09-10 13:02 ` Adrien Nader
2014-09-10 13:05 ` David Sheets
2014-09-10 14:04 ` Thomas Braibant
2014-09-10 14:13 ` Adrien Nader
2014-09-10 13:18 ` Mark Shinwell
2014-09-10 13:29 ` Francois Berenger
2014-09-10 13:53 ` Jacques-Pascal Deplaix
2014-09-10 13:55 ` Francois Berenger
2014-09-10 14:17 ` Maxence Guesdon
2014-09-10 19:13 ` Drup
2014-09-10 22:56 ` Gerd Stolpmann
2014-09-13 12:01 ` rixed
2014-09-13 12:21 ` Drup
2014-09-13 12:37 ` rixed
2014-09-13 12:50 ` Adrien Nader
2014-09-13 13:05 ` Drup
2014-09-19 11:15 ` Matej Kosik
2014-09-10 14:23 ` Gerd Stolpmann
2014-09-10 15:17 ` Leonardo Laguna Ruiz
2014-09-10 18:59 ` Yotam Barnoy
2014-09-10 19:16 ` Peter Zotov
2014-09-10 19:56 ` Sebastien Mondet
2014-09-10 20:15 ` Gabriel Scherer
2014-09-10 23:20 ` Gerd Stolpmann
2014-09-10 20:13 ` Adrien Nader
2014-09-11 7:53 ` Francois Berenger
2014-09-11 10:37 ` Yaron Minsky
2014-09-12 14:08 ` Yotam Barnoy
2014-09-12 14:31 ` Francois Berenger
2014-09-12 14:36 ` Anil Madhavapeddy
2014-09-12 18:49 ` Yaron Minsky
2014-09-12 15:10 ` SF Markus Elfring
2014-09-12 15:34 ` Adrien Nader
2014-09-12 18:50 ` Fabrice Le Fessant
2014-09-14 18:46 ` Richard W.M. Jones
2014-09-13 12:22 ` rixed
2014-09-15 13:34 ` Stéphane Glondu
2014-09-18 21:15 ` Yotam Barnoy
2014-09-18 21:21 ` Anil Madhavapeddy
2014-09-18 21:36 ` Yaron Minsky
2014-09-19 12:31 ` Daniel Bünzli
2014-09-19 13:06 ` Anil Madhavapeddy
2014-09-18 21:23 ` Yaron Minsky
2014-09-19 7:27 ` Gabriel Scherer
2014-09-19 15:03 ` Yaron Minsky
2014-09-12 16:54 ` [Caml-list] Re : " r.3
2014-09-14 18:16 ` [Caml-list] " Richard W.M. Jones
2014-09-19 9:14 ` r.3 [this message]
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=1839435586.73559263.1411118063407.JavaMail.root@zimbra27-e5.priv.proxad.net \
--to=r.3@libertysurf.fr \
--cc=caml-list@inria.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