From: Jurko GospodnetiÄ (jurko.gospodnetic_at_[hidden])
Date: 2008-07-23 05:14:58
> I need to embed a path generated from the install prefix into my library
> so it can find files at runtime. This isn't hard to do, since I can use
> a <conditional> requirement to generate <cxx-flags>-DMYPATH=... from
> <install-default-prefix>, but here's the problem. If the user uses bjam
> to build the library, and then calls bjam later and changes
> <install-default-prefix>, how do I get the library to rebuild with the
> new -D option?
My suggestion is to define a new composite, non-incidental feature.
However this is not supported for 'free' features that take 'any
text' as their value (because Boost Build currently encodes used
properties that affect the build as path to the built target and free
feature values would mess up that path). You would need to define a list
of possible tag values and then convert them to exact paths inside your
Hope this helps.
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