The normal $-style expressions are always allowed, but in program-syntax
mode, identifiers stand for variables, function application is the
f(e1, ..., e2) form, and there are the standard infix
operators. To switch back to the default syntax, use .LANGUAGE:
make

Note, shell commands and rules never use program syntax, except within
function arguments.

This is not heavily tested.

Added support for partial and curried function applications. Normal
funcation application still require using the correct number of arguments
(as relaxed by the introduction of optional arguments), but apply
function can be used to create curried and partial applications.

Note: this is, of course, not the same as imperative programming, because
functions can always choose not to export. In particular, the string
"functions" do not export.

public.X = 1
export X
public.f() =
X = 2
Y = $"$f"
# X = 1
# Y = 2

Added .STATIC and .MEMO rules - an enhanced, yet lazy
(delayed) version of the static. sections.

Basic usage:

.STATIC:
println(foo)
X = 1
Y = $X

The variable X is exported, with a "delayed" value. The rule is
only evaluated if the value for $X is needed, but it is lazy. The definition of Y does not force evaluation.

.STATIC rules allow dependencies, for example:

.STATIC: x.input
X = $(expensive-function x.input)

This is be evaluated if x.input changes and X is forced.

.STATIC rules also allow explicitly specifying which
variables are exported, for example:

.STATIC: X: x.input
Y = 1
X = $Y

Here, Y is not exported from the section.

By default, if a .STATIC rule is evaluated several times (for example,
if the .STATIC rule is present inside a body of a function that is
called several times), the result is the same set of delayed
variables.

.STATIC rules can have :key: dependency that
specify whether we are getting the same set of delayed variables or not, when
re-executing the same .STATIC rule. For example,

Built-in awk will now set the FILENAME and
FNR ("line number") variables when evaluating its body.

The run-time is now included in - exit messages (e.g.
when
--print-exit is enabled) - bug 680. Note that
this only indicates when OMake have noticed that the command have
finished, which may be quite inaccurate in parallel builds (where OMake may be
busy setting up parallel jobs and not paying attention).

Significant code reorganization in preparation for OMake 0.9.9, should
be largely transparent to the end-users

The 3-place rules are now considered implicit and will be inherited by
subdirectories. This makes it easier to declare default rules for common
targets, such as

clean: %:
rm -f ...

Allow .PHONY sections to have a body. A .PHONY
declaration with a body would create a default (implicit) rule for the newly
created phony target(s).

Detect case-insensitive filesystems on Unix-like operating systems
(especially common under Mac OS X). This should make it possible to use
OCAMLDEP_MODULES_ENABLED=true under Unix-like operating systems
with case-insensitive filesystems.

Changed the default value for the OCAMLDEP_MODULES_ENABLED to
$(OCAMLDEP_MODULES_AVAILABLE). In other words, ocamldep
-modules will be used whenever it is available (e.g. under OCaml 3.10
or if the bytecode executable distributed with OMake can be used).

A number of performance improvements. In particular, the size of the
.omakedb should now be significantly smaller.

The main change in this release is that the OMake values will now be
converted into the shell command lines directly (all the previous versions
of OMake should first "flatten" the value into a string and then perform
sh-like parsing of the resulting string). In particular, this means
that:

All the special symbols in files and directory values will be
preserved.

All the spaces inside the array elements will be preserved.

All the special symbols in OMake-quoted values
($"..." and $'...') will be preserved.

If the first element of the command line is a file value, neither
PATH- nor alias-expansion will be performed. Note - there will also be no
alias-expansion if the executable value contains quoted parts or starts
with a \.

The Shell. aliases will now receive the values passed on the
shell command line as is, not the string-expanded version. Also, if some
of the arguments are the result of a glob-expansion, the alias function
will receive the appropriate file values, not the strings.

OMake 0.9.8 will not be fully backwards-compatible with the earlier
releases.

There are now a number of indices, including a index of variables, an
index of functions, and an overall index.

OCaml.om improvements:

Implemented a new approach to computing the dependencies in OCaml
projects in OMake. In this approach a special version of ocamldep
is used to only extract the list of the external modules a file depends on
and then OMake is used to map those modules to files in the include path.
This eliminates the "standard" deficiency of having to generate all the
relevant OCaml source files before ocamldep is called. This
feature is considered highly experimental and is disabled by default. Use
the OCAMLDEP_MODULES_ENABLED variable to enable.

Added support for the Menhir parser-generator (experimental).

C.om improvements:

Changed the CProgram function to consider LIBS to be the actual
library files (_without_ the extension) that need to be linked in.

Improved the C scanner rule on Windows.

LaTeX.om improvements:

BSTINPUTS environment variable joins TEXINPUTS and
BIBINPUTS in the list of variables initialized from the OMake's
TEXINPUTS variable.

The list of such variables is now configurable (TEXVARS variable
contains an array of names).

More control over the OMake output and verbosity.

By default, OMake is now much more silent ("-S
--progress" is enabled by default when it outputs to a terminal,
and "-S" is enabled in all other cases).

Added a
--verbose option that would make OMake very verbose, when needed.

Added an ability to postpone and/or repeat the rule execution output (so that, for example,
only the output of the rules that fail is printed, or the output of the
rules that failed is repeated at the end of the omake -k
execution). This feature is somewhat experimental and might change in the
future versions of OMake.

Added the -o option for better control of OMake verbosity.

Added three special .PHONY targets: .BUILD_BEGIN,
.BUILD_SUCCESS, and .BUILD_FAILURE.
.BUILD_BEGIN is built before anything else in your project. One
of .BUILD_SUCCESS or .BUILD_FAILURE is built when the
build for your project terminates.
Note:

This feature is experimental and is likely to change in the
future versions of OMake.

If you want to use these targets, you should probably add them to
your ~/.omakerc, rather than adding them directly to each of
the projects you work on.

OMake will now save the .omakedb periodically, preventing the
state loss in case the OMake process dies unexpectedly (for example, when Cygwin
kills OMake after user presses Ctrl-C). The checkpointing interval may be
configured both at compile time and via the command line.

The variables such as $< and $@ in rules and
% in implicit rules will no longer be expanded to strings; instead
they will be passed as Node ("file") values.

Much better handling of the exit function, a number of bugs fixed.

Implicit rules can no longer have target patterns referring to another
directories. See bug #456 for
detail.

Improved support for configure-style scripts in OMake (using the
run-once static. sections). OMake installation now includes a small
library of useful helpful configure functions and a number of examples
(ncurses, readline, fam).

LaTeX rules improvements, including support for TeTeX v.3 and better
pdflatex support.

The which function should now work correctly in Cygwin. Fixed
a number of issues related to using ocamlfind under Cygwin and
Windows.

Fixed a number of bugs related to execution of complex shell
pipelines.

Fixed a problem with interactive osh sessions not handling the
return operator correctly.

Improved handling of implicit :value: dependencies (implicit
value dependencies are added for all the “free”variables in
section eval). The free variable computation is more precise, and
the implicit dependencies are now allowed to contain undefined variables.

The include foo directive will now try opening foo.om
before trying to open foo. Same is true for the .INCLUDE
rules.

A number of documentation fixes.

Significant changes in the setup for compiling OMake. No more autoconf,
bootstapping uses make to build a feature-limited bootstrapping binary and
the normal version of OMake is compiled using OMake itself. Makefiles are
now generated by OMake.

Significant reorganization of the source three. Now the source three
has a reasonable directory structure, instead of a single flat directory
with all the files.

Added "static" sections that are evaluated once. Values defined
in static sections are persistent across runs of omake. This is
convenient for implementing configure-style tests in omake files.

Added :value: dependencies.

Value dependencies are specified using the :value: option in rules.

a: b c :value: $(X)
...

This rule specifies that "a" should be recompiled if the value of
$(X) changes (X does not have to be a filename). This is intended
to allow greater control over dependencies.
In addition, it can be used in place of other kinds of dependencies.
For example, the following rule:

a: b :exists: c
commands

is the same as

a: b :value: $(target-exists c)
commands

Notes:

The values are arbitrary (they are not limited to variables)

The values are evaluated at rule expansion time, so variables
like $@, $^, etc are legal.

One other significant difference is that the rule cache now uses a
digest of the rule commands text, not the text itself. This has an
impact on initial omake speed (I am not sure how significant it is)
but the cache is smaller. Also, "section eval" should now be
handled correctly.

Significantly changed the meaning of the .SCANNER rules. Now the
.SCANNER rules are treated much more like normal rules.

Externally, a .SCANNER rule has the usual rule form:

.SCANNER: target: dependencies...
...scanner commands...

However, the scanner target is now decoupled from the
build target, allowing a scanner result to be used for multiple
build targets. For example, ocamldep produces dependencies
for .cmo and .cmx files simultaneously. They can share
the scanner rule by specifying an explicit :scanner: dependency.

The current convention is that scanner targets should be named
scan-<language>-<source-file>.

If a rule has multiple :scanner: dependencies, the actual
dependencies will be the union of the scanner results.

The .SCANNER targets use a different namespace than
normal targets, so it is valid to have overlapping rules.

.SCANNER: foo:
echo "foo: boo"
foo: :scanner: foo
...

For backwards compatibility, if a rule has no :scanner:
dependencies, then omake will try to find a scanner with
the same name as the target. So in the example above,
the :scanner: foo is actually unnecessary.

Added file locking for the .omakedb and .omc files, so that multiple processes
can be run simultaneously.

Fixed issues where files were being expanded during the string to array
conversion.

Better accessibility of the build rules and dependencies from OMake scripts.

Added the vmount function to define a "virtual mount" of one directory
over another. This adds a fairly simple way to define multiple versions
of a project. Suppose your source files are in a directory src/. Then
one easy way to compile a version of the project is the following.

vmount(-l, src, x86)
.SUBDIRS: x86

Files from the src directory are now automatically linked into the
x86 directory as needed. If you want to have multiple versions,
you can use multiple directories (and multiple vmounts).

The Map object is now completely changed.

The keys are now "simple" values, not just strings. Simple
values include integers, floats, strings, arrays of simple
values, files, and directories.

Only the Map class has the map functions defined. If you want
to have, say, a File that also includes a Map, create a
subclass that extends both File and Map.

Literal string keys can be written in the form $|key...|.
This works both for definitions and uses. The usual modifiers
are allowed $,|key| and $`|key|.