Subject: Re: [boost] Problem cross-compiling boost.context for Raspberry Pi (2)
From: Oliver Kowalke (oliver.kowalke_at_[hidden])
Date: 2015-06-16 03:48:29
2015-06-16 9:28 GMT+02:00 Vladimir Prus <vladimir.prus_at_[hidden]>:
Depends on what value is correct. If the check can be formulated as
> compiling some
> source, or running some tools, then it can be done.
AFAIK it is very hard or nearly impossible for code to detect for which ABI
and/or binary format it is compiled for.
ABI/binary format are set/specified by flags in the compiler command line.
The address model can be detected over pointer size - but ABI ...?!
> However, unless I am mistaken, all ARM variants use <abi>aapcs - so maybe
> does not need to be detected at all, and can be removed from conditions?
For ARM this is true but not for the other architectures (MIPS for instance
has 4 different ABIs).
boost.context determines the default values for ABI/binary-format on the
values returned by 'os.name' and 'os.platform'.
I don't know another way for reliable ABI/binary-format detection in
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk