In my view, one of the nice things about Jam is that it gets away from
wildcard stuff. What's so hard about:
SourceFile foo.c ;
SourceFile bar.c ;
(etc)
If you can write the code for a file, then you can certainly add a line
to the Jamfile for it. And the really nice thing is, you can say what
*kind* of source file it is, even if the filename doesn't help:
ExtraOptimizedSourceFile zap.c ;
Furthermore, if you have any automatically generated *.c files, they
won't get picked up.
So anyway, you *can* do things like what you describe, but I actually
like having things listed out, better.
-Lex
Dominic WILLIAMS <d.wi...@csee-transport.fr> wrote:
Hello,
Thanks for your useful information on parallel builds on NT. One thing I
can say for Jam is that it has a friendly and competent user group !
With gnu make, I am used to listing source files automatically, e.g.
myprog: $(wildcard *.cpp)
This way, the makefile can be set up once and for all, and does not need
to be modified each time a new source file is added to the project. Is this
sort of thing possible using Jam ?
Dominic.
2 messages in com.perforce.jamming[jamming] automagically listing sourc...