cons-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: Cons with output in Separate Subdirectories.


From: Greg Spencer
Subject: RE: Cons with output in Separate Subdirectories.
Date: Fri, 17 Nov 2000 09:21:14 -0700

Giovanni,

        On Windows NT, using NTFS, Cons DOES make hard links.  I know it sounds
hard to beleive, but it is true.  The only bad thing about that is that the
MSDEV editor deletes files before saving them, so it doesn't preserve the
hard links (so you should use another editor).

        You need to understand that when your Conscript is evaluated is not when
the files are built.  It is evaluated first, and then after cons has
collected all the rules (by evaluating your Conscript tree), it builds the
things that need to be built.

        The reason it fills up memory when you make the source depend on the 
target
is that now the target depends on the source, and the source depends on the
target.  This makes an infinite dependency loop, and with recursive
evaluation of the dependencies, sucks up all available memory.

        If you need a program to run before the next one is built, you will 
have to
create a Command rule that runs the program and creates some output.  Then,
make your next program depend on this output.  Cons will then build things
in the order you want.

        As far as the Command rule itself, read the documentation -- it talks 
about
%< and %>.  No, they aren't escape characters for < and >.

        There is no optional package for Windows yet.  It's something we are
working on, and will have eventually.

        You simply need to add "debug" to the build types in the @types array to
build a debug build.  In my usage, it defaults to @types = qw(debug
release);

        I hope that helps.

                                -Greg.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]