|
Boost-Build : |
From: digiharmon (digiharmon_at_[hidden])
Date: 2002-03-27 17:47:43
> >
> >How hard would it be to factor out the OS and/or cpu from the
> >toolset? Is it actually a trivial matter? I don't understand the
> >internals well enough to know the answer.
>
> The trivial aspect of it is that all it would take is to add another
> subvariant feature to encompass the new orthogonal aspect. In this
case one
> might add a "platform" feature. Then the above coould become:
>
> flags gcc PLATFORM <platform> ;
> switch $(PLATFORM)
> {
> case NT*:
> flags gcc CFLAGS <threading>nulti : -mthreads;
>
> case SunOS*:
> flags gcc CFLAGS <threading>multi : -pthreads ;
> flags gcc LINKFLAGS <threading>multi : -pthreads ;
> flags gcc FINDLIBS <threading>multi : rt ;
> NO_GNU_LN = true ; # sun seems not to use the GNU linker with
>
> [...etc]
> }
>
We added a "platform" feature and it seems to work, except that we
cannot specify more than one feature on the jam command line using -
sBUILD=.
-sBUILD="debug <platform>x86-solaris" works.
-sBUILD="debug <platform>x86-solaris <runtime-link>dynamic" just
ignores the platform and uses the default platform.
It seems that specifying more than one feature on the command line
causes all the specified features to be ignored and the defaults are
used.
Has anyone else seen this behavior?
--Jerry
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