From: Aleksey Nogin <nogin@cs.caltech.edu>
To: godi-list@ocaml-programming.de, Caml List <caml-list@inria.fr>
Subject: Announcing OMake 0.9.6.5
Date: Wed, 14 Sep 2005 23:02:28 -0700 [thread overview]
Message-ID: <43290E74.1000506@cs.caltech.edu> (raw)
We are proud to announce the latest release of the OMake Build System -
OMake version 0.9.6.5.
OMake is a build system, similar to GNU make, but with many additional
features. The home site for OMake is http://omake.metaprl.org/ . OMake
features include:
o Support for 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, scriptable dependency analysis using
MD5 digests.
o Portability: omake provides a uniform interface on Win32, Cygwin,
and Unix systems including Linux and 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 files at once.
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.
OMake preserves the style of syntax and rule definitions used in
Makefiles, making it easy to port your project to omake. There is no
need to code in perl (cons), or Python (scons). However, there are a
few things to keep in mind:
1. Indentation is significant, but tabs are not required.
2. The omake language is functional: functions are first-class
and there are no side-effects apart from I/O.
3. Scoping is dynamic.
OMake is licensed under a mixture of the GNU GPL license (OMake engine
itself) and the MIT-like license (default configuration files).
OMake version 0.9.6.5 in mostly a bugfix release. The changes in this
version include:
- Improved support for configure-style scripts.
- LaTeX rules improvements.
- Fixed the "which" function and ocamlfind support under Cygwin.
- New built-in functions: get-registry (Windows-only), removeprefix,
html-string.
- Improved processing of complex shell pipelines.
- A number of documentation fixes.
- Numerous other bug fixes and improvements.
For a more verbose change log, please visit
http://omake.metaprl.org/changelog.html#0.9.6.5 .
Source and binary packages of OMake 0.9.6.5 may be downloaded from
http://omake.metaprl.org/download.html . In addition, OMake may be
obtained via the GODI packaging system (3.08 and "dev" branches).
To try it out, run the command "omake --install" in a project directory,
and modify the generated OMakefile.
OMake 0.9.6.5 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@metaprl.org and/or at http://bugzilla.metaprl.org/
--
Aleksey Nogin
Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Moore 04, tel: (626) 395-2200
reply other threads:[~2005-09-15 6:02 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=43290E74.1000506@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;
as well as URLs for NNTP newsgroup(s).