From: bmosher_at_crosswinds_dot_net (bmosher_at_[hidden])
Date: 2002-02-06 11:53:19
> Now I'm also confused... I missed the discrepancy initially...
Rene, you're not the only one that missed the discrepancy. I must be
a couple of drinks ahead of you. What I was trying to say was to
suppress the build of the <runtime-link>**static**. Go with your
original interpretation and you'll be on track with what I'm trying
to do. Good catch Dave.
> >....and why wouldn't use just put <runtime-link>dynamic in the
> > target requirements?
Dave, if I understand what you're saying, then something like this
# An executable called 'test'
exe test : baz_test.cpp
This will cause jam to only build the test executable dynamically? I
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. I
wish I were at the level of understanding to figure these things out
on my own. It would be nice to actually contribute something
reasonably intelligent to the conversation, rather than just
thrashing around saying "how do I do XYZ?" 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.
thanks again guys,
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