From: Reece Dunn (msclrhd_at_[hidden])
Date: 2006-06-19 11:23:09
Rene Rivera wrote:
> Rene Rivera wrote:
> > Vladimir Prus wrote:
> >> Rene Rivera wrote:
> >>> b) Not sure what you mean. But if you mean not being able to request
> >>> multiple variants from the command line, then I disagree.
> >> You can request several variants on the command line, as documentation says:
> >> http://boost.org/boost-build2/doc/html/bbv2/tutorial.html#bbv2.tutorial.hello
> > And a bjam invocation at the boost root of:
> > bjam -n -a --v2 --builddir=C:/Boost/build gcc-3.4.5~mingw~stlport51
> > --prefix=C:/Boost/install stage stdlib=stlport-5.1~gcc345 debug release
> PS. It produces the same error even without the
> "stdlib=stlport-5.1~gcc345". So it doesn't work regardless of variant
I have replicated this with the simpler:
bjam --v2 debug release
The problem here is related to the issue I mentioned in my previous post
(but that was for install targets).
As I understand this issue, the variant feature isn't being used in the
flex/bison generator (and the same for the install target), so you only
get a single virtual target for the LL/YY/install target specified.
There are two issues:
(1) for the LL/YY targets it is most likely to treat these targets as
variant independant, build them once, then build the debug and then
the release versions of the C/CPP virtual targets produced;
(2) for the install rule, it is unclear what is to happen here, however,
my suggestion would be to install the debug versions to the
specified location, then later install the release versions to the
same location (unless that location is altered by a tag or location
As for the STLport-specific issue, I haven't got a clue at the moment.
My feeling is that it is a seperate issue.
Express yourself instantly with MSN Messenger! Download today it's FREE!
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