Re: [Boost-build] #7706 : cross compiling of threads library - JamFile.v2

Subject: Re: [Boost-build] #7706 : cross compiling of threads library - JamFile.v2
From: Vicente Botet (vicente.botet_at_[hidden])
Date: 2012-12-11 05:10:42

Jürgen Hunold-2 wrote
> Hi Vicente,
> 
> On Monday, 10. December 2012 20:31:11 Jürgen Hunold wrote:
>> Hi Vicente,
>> 
>> On Monday, 10. December 2012 08:02:06 Vicente Botet wrote:
>> > Jürgen Hunold-2 wrote
>> > 
>> > So there is something wrong yet. I will try to understand better how
>> all
>> > this work.
> 
> Please find a (hopefully) better patch attached which combines the old 
> detection with a new selection method.

Hi,

after reading the patch I think that its use is similar to setting the
threadapi on the command line, that is, instead of doing

b2 threadapi=pthread

the user will do 

b2 target-os=linux

I'm not aware of who did the original design of Boost.Thread build
(Anthony?), but I don't think the patch is improving the current situation
significantly. As I understand it we are able to compile either using the
pthread or win32 api from a windows machine. 

The problem is that we can not set the default threadapi value in function
of the target-os instead of the os.name. Is there something that can be
improved on the Build system? 

What is wrong using directly the threadapi feature?
I don't know if it covers the cross compilation from linux to use the win32
api. Could some having a cross compiler try

b2 toolset='the cross compiler' threadapi=win32

on a non windows machine?

Best,
Vicente

--
View this message in context: http://boost.2283326.n4.nabble.com/7706-cross-compiling-of-threads-library-JamFile-v2-tp4639721p4639848.html
Sent from the Boost - Build mailing list archive at Nabble.com.