From: Rene Rivera (grafik.list_at_[hidden])
Date: 2006-03-27 02:16:25
Only noticed I might be able to answer some of this now :-)
Roland Schwarz wrote:
> Sorry for answering to my own post, but I looked into this more deeply
> and still more questions:
> The os feature is based on the jam $(OS) variable is it?
> If so, the variable reflects the platform jam was compiled on, not
> necessarily the platform the build is targeted for. E.g jam built with
> vc7, target platform is cygwin. So os will be of little help.
Not of little help, since it's the common use case to target the
platform one is running on. Although Cygwin is a special case. But then
again it should be handled differently than plain Win32/NT.
> Is there a concept of target platform in Boost.Build?
Only as a TODO item ;-)
> Of course the
> chosen toolset somehow implicitly carries this information too, but I am
> thinking about something available from boost/config.hpp where compiler
> and platform is separately factored out.
The only glimmer I have is this comment in the BBv2...
# This feature is used to determine which OS we're on.
# In future, this may become <target-os> and <host-os>
local os = [ modules.peek : OS ] ;
feature os : $(os) : propagated link-incompatible ;
> Would it be possible to get this platform information in bjam too?
I don't understand that question. Get which platform information? And is
that in bjam or Boost.Build?
-- -- Grafik - Don't Assume Anything -- Redshift Software, Inc. - http://redshift-software.com -- rrivera/acm.org - grafik/redshift-software.com -- 102708583/icq - grafikrobot/aim - grafikrobot/yahoo
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