platform dependant source files

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?

Yes.

> 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
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build

Rene Rivera wrote:
> 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.

Sorry this should have read: Of little help for what I have
in mind, 
i.e. deducing which platform the build is intended to go.

> 
>> 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?

Never nor. I am speaking about the config.hpp headers of the
boost library.

But as I am just recognizing also the config.hpp does not
give such 
information in the form of a macro definition. It just
defines 
BOOST_PLATFORM to some platform dependent string. e.g.
#define BOOST_PLATFORM "Cygwin".
What I was hoping for is something like
#define BOOST_PLATFORM_CYGWIN
if compiling for cygwin.

So perhaps the best I can do is rethinking my problem and
try to 
approach from a different angle.


_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build