From: Vladimir Prus (ghost_at_[hidden])
Date: 2008-04-23 01:02:29
On Wednesday 23 April 2008 02:27:29 Roland Schwarz wrote:
> Vladimir Prus wrote:
> > You can use cygwin gcc in both cygwin mode and -mno-cygwin mode. What
> > default threading api do you expect for the latter case, and can it be
> > inferred in any way from output of -dumpmachine?
> The default api possibly should be win32 in the latter case. In
> principle it could be infered from -dumpmachine by evaluating
> the flavor which would be in that case:
1. We codify that the important properties line cygwin/mingw should
be fixed for a given version configured in user-config.jam, and that
adding -mno-cygwin by hand is not OK.
2. -mno-cygwin actually changes the output of -dumpmachine?
> I have spent some thought about how to be able to have the compiler
> choice influence the default.
> My ideas are like so:
> 1) Make threadapi an optional feature
> 2) Change the <conditional> requirement to add a threadapi
> only if none specified yet and make it conditioned on
> flavor of compiler.
This seems like a good approach, except that we don't have this
'conditional feature as default' thing you appear to suggest above.
Or I musunderstood, and it's actually doable now?
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