From: DigiWays (boost.build_at_[hidden])
Date: 2005-07-06 16:26:53
VP> I should add that at the moment, the modifiers.jam and <version> feature are
VP> not used in V2. The logic for adding version number for Boost, for example,
VP> is precisely the same as in V1, and we don't yet have any problems with it.
VP> Basically, we just have a top-level rule that add version number of all
VP> library target names.
I understand that what I am trying to do is quite different from how
bbv2 is used to compile boost. With boost we only have one global
version number, and you are not supposed to mix Boost.Filesystem 1.28
with Boost.Thread 1.32. In my case I have several dozens of libraries
developed by different teams, and unfortunately it is not possible to
have single global releases. People just release new versions of their
libraries and specify the required minimum version numbers of
libraries they depend on. I.e. when someone releases new version of
"L1", they state that it requires "L2" v1.05 or newer and "L4" v1.15
or newer. Then it is up to the developer who maintains executable to
set, which versions of "L1", "L2" and "L4" he wants to use in a
particular version of his executable.
Do you think, bbv2 can suit these requirements (given that I can add
-- Valentin Samko http://val.samko.info
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