Re: [boost] linking on OSX

Subject: Re: [boost] linking on OSX
From: David M. Cotter (me_at_[hidden])
Date: 2009-10-21 13:27:55

i tried doing this:

./bjam macosx-version-min=10.4 architecture=combined linkflags="- 
force_cpusubtype_ALL" install

malkier:lib davec$ otool -f -v ./libboost_thread.dylib
Fat headers
fat_magic FAT_MAGIC
nfat_arch 2
architecture i386
     cputype CPU_TYPE_I386
     cpusubtype CPU_SUBTYPE_I386_ALL
     capabilities 0x0
     offset 4096
     size 119460
     align 2^12 (4096)
architecture ppc7400
     cputype CPU_TYPE_POWERPC
     cpusubtype CPU_SUBTYPE_POWERPC_7400
     capabilities 0x0
     offset 126976
     size 124024
     align 2^12 (4096)
malkier:lib davec$

On Oct 20, 2009, at 10:10 PM, Vladimir Prus wrote:

> David M. Cotter wrote:
>
>> from Chris again:
>>
>>> Just to follow up on this: there appears to be some odd (or at least
>>> non-obvious) behaviour with the linker in Xcode 3.2. If you set the
>>> deployment target to 10.3, the resulting architecture ends up as
>>> ppc7400 whereas 10.4 will give you ppc. (10.5 and 10.6 give you
>>> ppc7400.)
>>>
>>> Anyway, if you know your code will work on all PowerPC CPU subtypes,
>>> it looks like you could use the -force_cpusubtype_ALL linker flag (I
>>> haven't tried it).
>>
>> again: how do i do this using bjam?
>
> I think you meant "using Boost.Build". There are cflags and  
> linkflags properties
> that you can specify on the command line. E.g.
>
>        linkflags="-force_cpusubtype_ALL"
>
> Does this help?
>
> - Volodya
>
>
> _______________________________________________
> Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost