RE: [jamboost] Boost.Build Feature request

From: Puverle, Tomas (IT) (Tomas.Puverle_at_[hidden])
Date: 2004-09-21 09:11:20

> Now, everything start to use that debug version of 
> libB. This might not be a solution for you though.

Oh if things were only that easy! :)

This is unfortunatelly not an option.
We are talking about debugging applications which have hundreds or
milions of lines of code that take many hours to compile link etc.
Sometimes it is necessary to do this debugging live, and with all of the
libraries being debug the performance may be unnaceptable.

> I'm not sure this is possible. The boost test are written in 
> such a way as using the buillt libraries, not the installed ones. 

That would be fine, also.

> > #Note that you must:
> > #1) use "gcc" and not "g++" as the compiler (long story)
> 
> I think -sGXX=gcc parameter to bjam will do this

Yes, I already do that in my makefile I sent.

> > #2) add libstd.so
> > #3) add libsupc++.a as the last thing on the link line.
> > run_tests:
> > ?
> 
> I've tried running:
> 
> bjam -sGXX=gcc -n -sBUILD="<find-library>std 
> <find-library>supc++" in the
> 
> libs/format/test directory and the output is:

But can you still use the --prefix etc command line params?
And what about a complete test suite, that builds & runs all of the
tests?
I saw a Jamfile under tools/status that seems to do that, perhaps I can
reuse it?

<snip>

So my final few questions are:
1) Is there an agglomerated Jamfile that has all the tests already in
it?
2) Is it possible to give the --prefix etc. command line params to the
tests?
3) [Unaswered from previous email] Is it possible to ONLY build the
shared objects without the archives?
4) If the above aren't, do you think they would be reasonable feature
requests for some future version of Boost.build?
5) Am I asking too many questions? ;)

> Does that seem OK?

Once again, thanks for your help.

Tom 
--------------------------------------------------------
 
NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited.