[Boost-bugs] [Boost C++ Libraries] #4147: Use target-os instead of os in Jamfiles

Subject: [Boost-bugs] [Boost C++ Libraries] #4147: Use target-os instead of os in Jamfiles
From: Boost C++ Libraries (noreply_at_[hidden])
Date: 2010-04-24 18:29:03

#4147: Use target-os instead of os in Jamfiles
-----------------------------------------------+----------------------------
 Reporter:  Steve Soule <sts11dbxr@…>          |       Owner:                
     Type:  Bugs                               |      Status:  new           
Milestone:  Boost 1.43.0                       |   Component:  Building Boost
  Version:  Boost 1.42.0                       |    Severity:  Problem       
 Keywords:                                     |  
-----------------------------------------------+----------------------------
 In many of the Jamfiles in Boost, the "os" property is used to add
 libraries and defines appropriate to the target operating system.  But the
 "os" property doesn't give the target operating system; it gives the build
 operating system.  The "target-os" property gives the target operating
 system.  So these Jamfiles do the wrong thing when cross-compiling.

 According to Vladimir Prus on the Boost-build mailing list:

 "Yes, in most cases 'target-os' should be used. Please file bugs for
 libraries that use 'os'."

 The full list of Boost libraries that appear to have this problem is:

 asio
 iostreams
 thread

 I generated this list by doing "grep 'import os'" and filtering out the
 python files, so it may not be all that accurate.

-- 
Ticket URL: <https://svn.boost.org/trac/boost/ticket/4147>
Boost C++ Libraries <http://www.boost.org/>
Boost provides free peer-reviewed portable C++ source libraries.