Skip to content

Commit

Permalink
Preparing for a release.
Browse files Browse the repository at this point in the history
git-svn-id: http://svn.metaprl.org/svnroot/mojave/omake-branches/0.9.8.6@13199 5109f7fa-8300-0410-942d-a7a480986ffa
  • Loading branch information
nogin committed Oct 27, 2010
0 parents commit 4348f63
Showing 480 changed files with 259,748 additions and 0 deletions.
166 changes: 166 additions & 0 deletions CHANGELOG.txt
Original file line number Diff line number Diff line change
@@ -0,0 +1,166 @@
For a more verbose changelog, see http://omake.metaprl.org/changelog.html

OMake 0.9.8.6 [10/26/2010]
- Added keyword and optional function arguments.
- Added "program" syntax.
- Added support for partial and curried function applications.
- Added a high-quality C parser, LaTeX parser and LaTeX spellchecker
- New functions added: localtime, gmtime, mktime, normalize-tm, utimes,
digest-string, url-escaped, find-all, addprefixes
- Numerous bugs fixed

OMake 0.9.8.5 [08/07/2007]
- Fixed Ctrl-C handling on Windows (with now correctly interrupt OMake)
- Added .STATIC and .MEMO rules, allowing defining lazy computations and
lazy memoization maps
- Added export sections, making it much easier to manage variable scoping
- Fields in sub-objects can now be referenced directly
- Many new built-in and library functions
- Significant bug-fixes

OMake 0.9.8.4 [06/04/2007]
- Fixed a file descriptor leak
- A few other minor bug fixes

OMake 0.9.8.3 [06/01/2007]
OMake 0.9.8.2 [skipped]
- Made it easy to define default ("implicit") rules for phony targets.
- Detect case-insensitive filesystems on Unix-like operating systems
(especially important under Mac OS X).
- A number of performance improvements.
- Documentation improvements.

OMake 0.9.8.1 [03/16/2007]
- Added a large number of new built-in and standard library functions
- Extented the autocomfiguration section of the standard library
- A number of improvements in the interactive osh shell.
- A number of improvements in the library of standard build recipes
- Documentation improvements.
- A number of other improvements and bugfixes.

OMake 0.9.8 [12/11/2006]
- The conversion from OMake expressions to shell command lines went through
a major redesign to make it more consistent and less ad-hoc.
- OMake documentation was significantly reorganized.
- OCaml build rules: Added experimental improved dependency scanner using
the upcoming "ocamldep -modules" feature; added support for the Menhir
parser-generator.
- Added a number of new options to control OMake's output and verbosity;
OMake is now more silent by default.
- Many more improvements and bug fixes.

OMake 0.9.6.9 [04/11/2006]
- Significantly improved C++ support; minor improvements in OCaml support.
- Significantly updated the default (sample) OMakefile.
- Significantly improved the performance of the built-in find command.
- Several other bug fixes and improvements.
- A number of documentation fixes and improvements.

OMake 0.9.6.8 [01/23/2006]
- Fixed a bug in PATH-expansion for pipelines.
- Improved the handling of the ".PHONY" nodes.
- Added a remove-project-directories function.
- Documentation fixes.
- A few other bugfixes and improvements.

OMake 0.9.6.7 [12/28/2005]
- Added basic support for C++.
- Portability improvements.
- OCaml.om improvements.
- Minor documentation fixes.
- A few other bugfixes and improvements.

OMake 0.9.6.6 [11/05/2005]
- Made sure OMake compiles fine with both OCaml 3.08 and 3.09.
- A few minor bugfixes and improvements.

OMake 0.9.6.5 [09/14/2005]
- 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.

OMake 0.9.6 [07/17/2005]

- Added "static" sections that are evaluated once.
- Added :value: dependencies, where a target depends on a computed
value, rather than a file.
- Changed the meaning of the .SCANNER rules. .SCANNER rules
are now much more similar to normal rules.
- Added file locking for the .omakedb and .omc files.
- Fixed issues where files were being expanded during the string->array
conversion.
- Rule execution now fails when any shell command fails, even those in
nested sections.
- Regular expressions now handle \(...\) arguments correctly. Also, the
lexer has better performance, searching is now roughly linear time.
- Added .SUBDIRS bodies, which can be used instead of the OMakefile
in a subdirectory.
- Added the vmount function to define a "virtual mount" of one directory
over another.
- Better accessibility of the build rules and dependencies from OMake
scripts.
- Improved the latex-related rules.
- The Map object is completely changed.
- Other bug fixes and improvements.

OMake 0.9.5 [skipped]

OMake 0.9.4 [01/04/2005]
- 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 the 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.3 [10/18/2004]
- OMake now supports ocamlfind in its default configuration file
(thanks to Bardur Arantsson for the initial patch).
- OMake should now also work with OCaml 3.07 (in addition to 3.08).
- A large number of bug fixes, including:
o OMake should now compile correctly under Cygwin (thanks to
Peter Jolly who provided the patch),
o "double-colon" rules (that allow specifying multiple rules for
the same target) should now work correctly,
o kqueue-based file system monitoring (Mac OS X, FreeBSD) should
now work correctly
o array definitions should now work better.
- Added a work around for the command line length limitation of
lib.exe on Windows
- Filesystem monitoring functionality now provides a choice whether
to continue monitoring once the project is built successfully.

OMake 0.9.2 [09/08/2004]
- Bugs fixed:
o "make install" will no longer create $HOME/.omake as root;
o the -custom option is now a part of OCAML_BYTE_LINK_FLAGS and
can be easily disabled;
o omake should now allow specifying dependencies for the same file
more than once.
- The OMakeroot.src, OMakeroot.default and OMakefile.default are now
under MIT license to allow users to freely borrow from them into their
own omake build files. (The rest of OMake is still under GPL).
- Fixed a number of typos and formatting errors in documentation.
16 changes: 16 additions & 0 deletions COMMENTS
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
*** curry branch

- What happens to exports from curried functions?

curry.f() =
export
public.X = 1
fun() =>
println($X)

- The arity of a ValPrim is used for partial application,
but the arities are often wrong.

- It is assumed that a primitive function, when partially
applied, takes -all- the keyword arguments. Nearly
all the primitives will choke if passed a keyword.
129 changes: 129 additions & 0 deletions INSTALL
Original file line number Diff line number Diff line change
@@ -0,0 +1,129 @@
-*- Mode: text; fill-column: 70 -*-

omake is designed to build itself. Of course you must be wondering
how we build in the first place!

If you already have a working copy of omake (for instance, by
downloading and installing it from somewhere else like
omake.metaprl.org), then you should use your working copy to do the
bootstrap.

Otherwise, let's assume you do don't have omake already installed and
you want to build it.

-- Bootstrapping --

Bootstrapping is setup to use "make" or "nmake". By using one of
these other tools, you can build a limited byte-code version of omake
that you can then use to complete the install.

NOTE: The bootstrap uses the file src/Makefile and src/Makefile.nt
with default options, like CC=cc. If something goes wrong, you can
edit these files by hand to suit your taste. However, the
src/Makefiles are generated, and they will be clobbered when you
run omake for the first time. To be safe, if you decide to modify
them, save your changes in some safe place, not /tmp.

-- Unix, MacOS X, Cygwin bootstrap --

You can use "make" to build a bootstrap version of omake. Run

% make bootstrap

to build the omake-boot executable. This should work with classic
make; there should be no need to use GNU make. If you have it, GNU
make will work fine.

If you are going to compile OMake with the default options, you can
use make to both bootstrap and build omake:

% make all

or even bootstrap, build, and install it:

% make install

Environment variables:
- PREFIX (make all, make install) specifies the prefix for OMake
installation (defaults to /usr/local)
- LIBDIR (make all, make install) specifies the location for OMake
library directory (defaults to $PREFIX/lib)
- BINDIR (make install) specifies the location for OMake binaries
(defaults to $PREFIX/bin)
- INSTALL_ROOT (make install) specifies a "packaging root" for the
installation. Namely, omake will be installed under
$INSTALL_ROOT/$LIBDIR and $INSTALL_ROOT/$BINDIR, but the omake binary
will be compiled to look for its files under $LIBDIR.

Please note that the first time OMake is built, the PREFIX, LIBDIR and
BINDIR variables are wrtten into the .config file in the root of the
sources tree. If the .config file exists, then the variables present there
have precedence over the environment variables.

-- Win32 bootstrap --

The native Win32 build is faster than a Cygwin executable; it is
recommended. However, no matter what you do, execution times on Win32
will be substantially longer than on Unix (I'm not sure why; I'm
guessing that Win32 is a pig).

NOTE: Note that if you call any native executable from a Cygwin
shell, and you signal it (for example, with control-C), Cygwin
immediately terminates the process. This is a well-known problem
with Cygwin. It also means that when you abort omake from a Cygwin
shell, it will not have a chance to save its work. Next time you
run omake, it will have forgotten everything it did before you
aborted it. Please complain to the Cygwin people at www.cygwin.com
if you would like this to change. Please be nice. They already
know about this issue.

One way to avoid this problem is to run omake from a dos-prompt.
You can also run osh in a console window if you want a usable
shell.

For a native Win32 build, you will need the native Win32 version of
OCaml, Visual C++, and the Microsoft macro assembler. See
www.ocaml.org if you want to know where to get the macro assembler
"ml". It once came with Visual C++, but as far as I know, this is no
longer true.

"nmake" is Microsoft's attempt at a build tool. It is part of Visual
C++. To run it, use the following command from a dos prompt.

dos> nmake -f Makefile.nt bootstrap

This will build the omake-boot executable, which you can use to finish
the installation.

-- Finishing the install --

Let's assume that you have successfully created the omake-boot
executable. To complete the install, run

% ./omake-boot
or
dos> omake-boot

After some configuration message, you should now get a message telling
you that a .config file was just created, and you should edit it.

You should either edit the .config, or leave it like it is. The
defaults should be pretty reasonable for your machine, but take a look
if you are curious.

When you are ready, run omake-boot again to build the real version of
omake.

If you like, you can run

% ./omake-boot install
or
dos> omake-boot install

to install it. At this point, you are done.

NOTE: You can continue to use omake-boot for building omake, but
you are probably better off using an installed version, or
src/main/omake. This is mainly for Win32, where the byte-code
omake-boot is not nearly as fast as the native-code
src/main/omake.
Loading
Oops, something went wrong.

0 comments on commit 4348f63

Please sign in to comment.