From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-02-06 13:42:18
----- Original Message -----
From: "bmosher_at_crosswinds_dot_net" <bmosher_at_[hidden]>
> Dave, if I understand what you're saying, then something like this
> should work?
> # An executable called 'test'
> exe test : baz_test.cpp
> : <runtime-link>dynamic
> This will cause jam to only build the test executable dynamically?
> didn't realize the 'requirements' section could include properties
> other than <include>, <define>, etc. If this is true then nicely
> done! Color me sheepish.
> Sorry to say, I am still at the point where I rely on the
> build_system.htm doc and the jam files in cvs to guide my usage.
The docs /should/ be enough to indicate that you can do this. Nothing in
the docs say that you can only put free features in the requirements
section. Maybe a broader range of examples would help, though.
> wish I were at the level of understanding to figure these things out
> on my own.
I don't want people to have to read the source (especially the current ugly
source) to understand how to use the system.
> It would be nice to actually contribute something
> reasonably intelligent to the conversation, rather than just
> thrashing around saying "how do I do XYZ?"
Those questions are very useful too.
> I have a reasonable
> working knowledge of jam and write my own rules occasionally, but I
> still haven't had that "Ah ha" moment with the jamboost system. I
> think the piece that continues to elude me is how the target
> properties interact with rules. For example, reading through the unit-
> tests.jam in cvs had me totally lost I'm afraid. Clues wanted.
That's just a bunch of code for testing some of the core rules of the build
system. In general it wouldn't help you understand much about how to use the
Boost-Build list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk