From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2008-03-20 10:01:18
When specifying an install target one must make sure that
the target file name is unique. E.g. for libraries this
usually is accomplished with the <tag> feature.
I ran into the problem that my target names must be the
same altough they come from different build variants.
So my question:
Is there a way to specify that I don't care which of
the versions will make the finally installed file?
I just must make sure there is one at least.
Background: As having posted in another mail I end up
having "different" *.hpp files, output from a code
generator. Their difference however is only because
unrelevant features cause the files to go into different
directories. The codegenerator does not make any use
of the features.
I guess a similar situation exists when generating
documentation when at the same time multiple build
variants are beeing requested. How is this solved in that
case? Can I possibly learn from this?
-- _________________________________________ _ _ | Roland Schwarz |_)(_ | aka. speedsnail | \__) | mailto:roland.schwarz_at_[hidden] ________| http://www.blackspace.at
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