From: Roland Schwarz (roland.schwarz_at_[hidden])
Date: 2006-03-26 07:16:44
Vladimir Prus wrote:
> You can also use the 'alias' rule to your advantage:
>
> lib thread : universal_source.cpp platform_sources ;
> alias platform_sources : a.cpp : <os>NT ;
> alias platform_sources : b.cpp : <os>LINUX ;
This one looks promising. Thank you. But I have a couple of additional
questions:
1) Where can I find which values for <os> do exist? Ideally I would
expect the list to be of the same values that the BOOST_PLATFORM from
the config headers can take. I suspect that this mechanism would need to
be embedded into the Boost.Jam core, true?
2) Does this work also for Boost.Build-v1? If not, how would I work
around this then?
3) Is it still required that the boost lib must be buildable with v1? At
least the standard setting of boost-build.jam in boost-root makes me
believe so.
Thank you,
Roland