Re:Re: [boost] Re: Re:Re: Re:Re: additional boost libraries?
Rene Rivera wrote: Robert Ramey wrote:
a) If the compiler is an older compiler b) && SPIRIT_ROOT is defined to something not null c) || the compiler is a newer compiler.
I think the build jamfile could altered to do this. I spent a little time at it but didn't immediately see how to do it. But I think it should be possible. Its probably trivial for a BJAM guru - so feel free anyone. Also it would be nice if it echoed a comment indicating that its skipping the XML components for lack of SPIRIT_ROOT.
Although it's now possible to do this, I would *not* recommend this as a solution. The basic problem with changing the Jamfile to skip the building is that it will only work if people use the Jamfile. That's fine for testing, but not for release. Many people out there don't use BB for building Boost.
Well, if boost build isn't being used then there is no issue. Such users would just exclude libs/serialization/src/*xml*.cpp files from the library build. This is what I would like to see the boost build system do. Seems by far the simplest to me. Robert Ramey
Robert Ramey wrote:
Rene Rivera wrote:
Robert Ramey wrote:
a) If the compiler is an older compiler b) && SPIRIT_ROOT is defined to something not null c) || the compiler is a newer compiler.
Although it's now possible to do this, I would *not* recommend this as a solution. The basic problem with changing the Jamfile to skip the building is that it will only work if people use the Jamfile. That's fine for testing, but not for release. Many people out there don't use BB for building Boost.
Well, if boost build isn't being used then there is no issue. Such users would just exclude libs/serialization/src/*xml*.cpp files from the library build. This is what I would like to see the boost build system do.
Hmm, good point :-) But after look at how to do this I realize that I was wrong, it's not currently possible. It's possible if the final target is a DLL or EXE, but because of the way that LIBs work on some platform it's not possible to easily combine them during the build :-( Let me think about how to do this... I'll get back to you, hopefully with a solution. PS. This is something that BBv2 supports already. Many more things are possible in BBv2 because of the explicit toolset configuration, as opposed to the implicit toolset config of BBv1. -- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com - 102708583/icq
participants (2)
-
Rene Rivera -
Robert Ramey