Roland Schwarz wrote:
> Volodya,
>
> yet another question:
>
> Why use a different mechanism for python, qt and boost
pre-builts?
Because python cannot be built using Boost.Build, and
because for Qt,
the official build system is not Boost.Build. For Boost, we
have
the luxury of being able to create whatever we want. Also,
both python
and qt have additional functionality, it's not just linking
to libraries.
>
> I.e. some libs have to be activated in user-config.jam
on a per user
> basis, others like boost are to be activated on a per
project basis (at
> the price of the project Jamroot not beeing platform
independent any
> more - the install path is coded into use-project ).
You can have 'use-project' in user-config.jam. Remember that
user-config.jam
is essentially a project.
> Do you suggest using separate Jamroot files for other
pre-built libs
> too, that have a naming that cannot be recognized
natively by the linker?
For a prebuilt libs that are not created with Boost.Build,
we'd have to
use the current approach of duplicate some-other-lib.jam
into the 'tools'
directory -- as we cannot expected
$prefix/share/whatever/Jamroot
will exist.
- Volodya
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
|
