Re: [Boost-build] generating headers out of Jamfile

Subject: Re: [Boost-build] generating headers out of Jamfile
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2011-01-30 08:49:21

Am 30.01.2011 14:08, schrieb Vladimir Prus:
> Oliver Kowalke wrote:
>
>> Am 30.01.2011 13:49, schrieb Vladimir Prus:
>>> Oliver Kowalke wrote:
>>>
>>>> Am 29.01.2011 09:17, schrieb Vladimir Prus:
>>>>> Oliver Kowalke wrote:
>>>>>
>>>>>> Am 29.01.2011 08:59, schrieb Vladimir Prus:
>>>>>>> FWIW, I am working on a patch to have those features always set for gcc, and
>>>>>>> hopefully for other compilers for which they can be reliably inferred. It's the
>>>>>>> top thing on my Boost.Build queue.
>>>>>>
>>>>>> that are good news - what is your time-frame for this feature?
>>>>>
>>>>> I think I have the hardest bit done. Should complete in a week or so (on trunk).
>>>>
>>>> do you consider ABI (sysv, eabi, aapcs, etc.)
>>>
>>> Not really. Can you actually change abi that a given g++ binary uses?
>>>
>>>> and Binary-Format
>>>> (elf,mach-o, etc.) too?
>>>
>>> Again, I don't think you can change this, for given architecture/target-os. Am I wrong?
>>>
>>> - Volodya
>>
>> you are not wrong but I won't change the abi or binary-format - I'd like
>> to use both properties to select the correct assembler code in the Jamfile.
>
> Should not you then be able to use architecture and target os, for the same purpose?

sure target-os and architecture are used for the selection too (I use 
<architecture>,<instruction-set>,<address-model>,<abi>,<binary-format>).

<abi> and <binary-format> are required because the target os may support 
different ABIs (for instance MIPS supports multiple ABIs: o32, n32, n64, 
o64, eabi) or binary-formats (MAC OS X: elf, mach-o).

Oliver