Version française
Home     About     Download     Resources     Contact us    

This site is updated infrequently. For up-to-date information, please visit the new OCaml website at

Browse thread
[Caml-list] Announcing the OMake build system version 0.9.1
[ Home ] [ Index: by date | by threads ]
[ Search: ]

[ Message by date: previous | next ] [ Message in thread: previous | next ] [ Thread: previous | next ]
Date: -- (:)
From: Marcin 'Qrczak' Kowalczyk <qrczak@k...>
Subject: Re: [Caml-list] Announcing the OMake build system version 0.9.1
Christian Lindig <> writes:

> 	Jam - like Make, but has procedural abstraction: a program is
> evaluated to build up the dependency tree. Unlike Make, clean
> separation of phases: analyzes the file system, makes a plan, and
> executes it. Hence, no checking the file system while executing the
> plan. Similar tools: Cons, SCons.

If changes to a module didn't result in changing its interface, my
compiler is careful to not overwrite the interface file, so modules
depending on this module will not be recompiled by make.

How does Jam deal with this? Before we compile a module, we don't know
whether modules which use it will need to be recompiled.

Of course it can conservatively assume that they always will be, but
then it's a disadvantage compared to make.

   __("<         Marcin Kowalczyk

To unsubscribe, mail Archives:
Bug reports: FAQ:
Beginner's list: