From: David Abrahams (david.abrahams_at_[hidden])
Date: 2002-05-17 07:07:53
----- Original Message -----
From: "Markus Schöpflin" <markus.schoepflin_at_[hidden]>
> After thinking further on this, I tried the following:
> MY_COMMON_PROPERTIES =
> variant my_common :
> variant my_debug : my_common :
> debug features ...
> variant my_release : my_common :
> release features ...
> BUILD ?= my-debug my-release ;
> Now if I only could get the build system to generate target
> paths that are just a combination of toolset and variant
> and explicitly specified features, my problems would be
It should already be doing that... what's actually happening?
Actually what you really want (IMO) is to have it leave out any elements
from the subvariant path which correspond to target requirements.
> Any hint where in boost-base.jam I might start looking?
I don't know; Rene might have one, but I might discourage him from looking
at it ;-)
> Or is this task hopeless?
Not hopeless, but /not/ wanting to keep hacking this stuff ourselves is one
reason v1 development has stopped in favor of v2.
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