From: Aleksey Nogin <nogin@cs.caltech.edu>
To: Caml List <caml-list@inria.fr>, godi-list@ocaml-programming.de
Subject: Announcing OMake 0.9.4
Date: Tue, 04 Jan 2005 20:33:03 -0800 [thread overview]
Message-ID: <41DB6DFF.6090400@cs.caltech.edu> (raw)
The OMake Team is proud to announce a new release of the OMake Build
System - OMake 0.9.4.
OMake is a build system, similar to GNU make, but with many additional
features:
o Support for large projects spanning several directories or
directory hierarchies.
o Comes with a default configuration file providing support for
OCaml, C and LaTeX projects, or a mixture thereof.
Often, a configuration file is as simple as a single line
OCamlProgram(prog, foo bar baz)
which states that the program "prog" is built from the files
foo.ml, bar.ml, and baz.ml.
o Fast, reliable, automated dependency analysis using MD5 digests.
o Portability: omake provides a uniform interface on Win32 and
on Unix systems including Linux and Mac OS X.
o Builtin functions that provide the most common features of
programs like grep, sed, and awk. These are especially useful on
Win32.
o Full native support for rules that build several things at once
(such as ocamlopt building .cmx and .o).
o Active filesystem monitoring, where the build automatically
restarts whenever you modify a source file. This can be very
useful during the edit/compile cycle.
o A companion command interpreter, osh, that can be used
interactively.
The home site for OMake is http://omake.metaprl.org/
OMake version 0.9.4 contains a large number of enhancements and bug
fixes, including:
- Portability improvements. OMake should now compile and work under
Windows 2000, Windows NT and FreeBSD. A number of Windows-specific
bugs are fixed. A Windows installer is added.
- OMake now uses the built-in versions of the following commands:
cp, mv, mkdir, rm, rmdir, chmod
- Improvements to the filesystem watch functionality. In particular,
the build will now restart if a change to one of the OMakefiles is
detected.
- Added a USE_OCAMLFIND variable that can be used to force or prohibit
the usage of ocamlfind in a project (by default USE_OCAMLFIND is set
to true iff the ocamlfind executable is found in path).
- Added a "--force-dotomake" option to create all .omc and .omo files
under $HOME/.omake/cache and a "--dotomake" option to specify an
alternative to $HOME/.omake
- Added :squash: dependencies (that specify that a dependency must
be built, but when the dependency changes, it does not cause the
target to be rebuilt).
- OMake will now read ~/.omakeinit and ~/.omakerc files on startup.
- Improved the latex-related rules.
- Documentation improvements.
- Bugs fixed: 142, 153, 311, 313, 314, 316, 332, 333, 339, 350, 360,
361, 366, 367, 368, 374, 375. See
http://bugzilla.metaprl.org/buglist.cgi?bug_id=142,153,311,313,314,316,332,333,339,350,360,361,366,367,368,374,375
for details.
OMake 0.9.4 is still an alpha release. While we have made an effort to
ensure that it is bug-free, it is possible some functions may not behave
as you would expect. Please report any comments and/or bugs to the
mailing list omake at metaprl.org and/or at http://metaprl.org/bugzilla
OMake is distributed under the terms of the GNU General Public License.
OMake configuration files are distributed under the terms of an MIT-like
license. OMake sources, as well as a number of Linux and Windows
binaries are available from the OMake home page at http://omake.metaprl.org/
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Jorgensen 70, tel: (626) 395-2907
reply other threads:[~2005-01-05 4:33 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=41DB6DFF.6090400@cs.caltech.edu \
--to=nogin@cs.caltech.edu \
--cc=caml-list@inria.fr \
--cc=godi-list@ocaml-programming.de \
--cc=omake@metaprl.org \
/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