[prev in list] [next in list] [prev in thread] [next in thread] 

List:       boost-build
Subject:    Re: [Boost-build] Wrong target-os with cross-compiler
From:       Steve Soule <sts11dbxr () gmail ! com>
Date:       2010-04-25 19:36:10
Message-ID: 4BD499AA.80803 () gmail ! com
[Download RAW message or body]

On 04/25/2010 11:09 AM, Rene Rivera wrote:
> On 4/23/2010 7:38 PM, Steve Soule wrote:
>> My computer is running Suse Linux 11.2, and I have the MinGW gcc windows
>> cross-compiler installed.  But when I use the cross-compiler, Boost
>> Build mistakenly sets the target-os property to "linux" instead of
>> "windows".  So I can't build with just:
>>
>> bjam toolset=gcc-mingw
>>
>> I have to do:
>>
>> bjam toolset=gcc-mingw target-os=windows
>>
>> Also, because the default is "linux", it adds "target-os-windows" to the
>> build path.
> 
> This is intentional.
> 
>> Shouldn't Boost Build figure out the default target-os automatically?
> 
> It does.. But it defaults to target-os == host-os. Perhaps you are
> thinking of some other useful default? If so, how would we automatically
> know to pick that other default?

In my opinion, the default value of target-os should be the target os of
the compiler being used.

With gcc, if you do "gcc -v", you get a dump of its build properties,
which generally includes something like:

--target=i686-pc-mingw32

if the target is different from the host.  I don't know about other
compilers.
_______________________________________________
Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost-build
[prev in list] [next in list] [prev in thread] [next in thread]