Re: [Boost-build] "os" versus "target-os"

Subject: Re: [Boost-build] "os" versus "target-os"
From: Steve Soule (sts11dbxr_at_[hidden])
Date: 2010-04-25 15:40:59

On 04/25/2010 10:53 AM, Christian Auby wrote:
> On 4/24/2010 8:31 PM, Steve Soule wrote:
>> On 04/24/2010 03:07 AM, Vladimir Prus wrote:
>>> On Saturday 24 April 2010 04:46:27 Steve Soule wrote:
>>>> I've noticed that many of the Jamfiles in Boost make use of the "os"
>>>> property.  For example, in libs/asio/example/http/client/Jamfile.v2,
>>>> this property is used to link in the right networking libraries and
>>>> define the appropriate defines depending on the os.  I haven't found any
>>>> documentation on the "os" property, but I would guess that it contains a
>>>> tag for the operating system on which the build is taking place.
>>>>
>>>> Shouldn't these be using the "target-os" property rather than "os"?  I
>>>> would think that when you're cross-compiling, target-os and os could be
>>>> quite different, and you would want to link the appropriate libraries
>>>> for the target operating system, not the build operating system.
>>>
>>> Yes, in most cases 'target-os' should be used. Please file bugs for libraries
>>> that use 'os'
>>
>> Done.  The full list of libraries was:
>>
>> asio iostreams thread
> 
> Does this mean I don't have to manually link ws2_32 and pthread
> anymore? That would have been excellent. Always wondered about why I
> had to do that but figured that was how it was supposed to be.

I'm sorry, I wasn't clear.  I didn't fix anything; I just submitted a
bug report as Vladimir asked me to.

If the appropriate maintainers fix the "os versus target-os" bug, it
will not necessarily remove the need to manually link ws2_32, pthread,
and other libraries.  That's a different bug.  Perhaps you should submit
a bug report about that.