From: Kenneth Knowles <kknowles@berkeley.edu>
To: caml-list@inria.fr
Subject: [Caml-list] [ANNOUNCE] ocamlconf-0.2
Date: Sun, 28 Mar 2004 10:11:51 -0800 [thread overview]
Message-ID: <20040328181151.GA9841@tallman.kefka.frap.net> (raw)
Hi all,
Announcing ocamlconf-0.2; new in this release:
* A slightly different API (with radically improved backend) for specifying
targets, with more options for libraries and less for scripts.
* Better makefile, with doc targets for each format known to ocamldoc, and
generally better management of "make all" vs "make opt"
* Finer control over what is installed with findlib, and under what package name
* Many bug-fixes for combined C/ocaml libraries.
http://kenn.frap.net/ocamlconf/
http://kenn.frap.net/ocamlconf/ocamlconf-0.2.tar.bz2
----- cut here -----
Description of ocamlconf:
Ocamlconf is a build helper for ocaml programs. It takes a 'configure.ml'
and creates a 'configure' script. This script prompts for compile time toggles
and variable settings, and outputs an automatically-generated makefile.
Features:
* Simple "./configure; make; make install" operation.
* MakeMake module for outputting your makefile based on specifications
* Conf module for prompting the user for compile-time options, as well as
locating libraries (usually via findlib)
* Util module with some useful shell and string functions
How Good is the Generated Makefile?
* Makefile is about as simple as a hand-written one.
* Contains a 'normal' and a '.opt' target for each program or library
* Typical targets for: install, install-opt, uninstall, clean, distclean, doc,
* all, opt, byte, tar, gzip, bzip2
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
reply other threads:[~2004-03-28 18:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20040328181151.GA9841@tallman.kefka.frap.net \
--to=kknowles@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;
as well as URLs for NNTP newsgroup(s).