From: Kenneth Knowles <kknowles@uclink.berkeley.edu>
To: caml-list@inria.fr
Subject: Re: [Caml-list] [ANNOUNCE] Development versions: ocamlconf, ASPCC
Date: Wed, 3 Mar 2004 15:06:21 -0800 [thread overview]
Message-ID: <20040303230621.GB15359@tallman.kefka.frap.net> (raw)
In-Reply-To: <20040303195326.GA991@manzanita>
> That's good but I would prefer to use OCaml and avoid makefiles
> altogether, similar to how Python's distutils just uses Python. Then we
> could have more sophisticated build rules with fixed points etc. (as
> John Max Skaller described in a post a while back.)
Ok, well I totally agree with this, and if anyone has any fixpoint-based
building code, a grand build system could really be in the works...
Does ocaml ever really need fixpoints (except for the compiler itself)? If this
is to be ocaml-centric (like I assume python's distutils are) then it seems like
digests of files like Cook uses would be sufficient... TeX is the only thing I
know that needs fixpoint computations.
Besides that I see a lot of value in the semantic separation of configuration -
determine what requirements and options a site has - and building. I even like
the user interface of 'configure && make && make install'
If the make and the make install steps were written in ocaml, great. In
particular I think almost all of 'make install' should be handled by findlib, so
it really just needs (1) improvements to ocamlconf (2) build tool (3) probably
some more flexibility to findlib.
Kenn
-------------------
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
next prev parent reply other threads:[~2004-03-03 23:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 1:47 Kenneth Knowles
2004-03-03 5:16 ` Issac Trotts
2004-03-03 6:25 ` Kenneth Knowles
2004-03-03 19:53 ` Issac Trotts
2004-03-03 23:06 ` Kenneth Knowles [this message]
2004-03-03 19:56 ` David MENTRE
2004-03-03 20:29 ` Issac Trotts
2004-03-03 22:36 ` Kenneth Knowles
2004-03-11 11:09 ` Markus Mottl
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=20040303230621.GB15359@tallman.kefka.frap.net \
--to=kknowles@uclink.berkeley.edu \
--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