[issue23966] More clearly expose/explain native and cross-build target information

[Nick Coghlan]

Nick Coghlan added the comment:

Capturing some additional notes regarding the purpose of multiarch platform triplets. These triplets should unambiguously capture:

* syscall ABI (~= kernel)
* instruction set (IA-32, IA-64, PowerPC, ARM, ARM64, etc)
* endian­ness (big- or little-
* word size (32- or 64-)

The initial set of triplets from Debian covers GNU/Linux, GNU/Hurd and GNU/FreeBSD. Issue 23969 covers accurately capturing Mac OS X details, while issue 23670 covers iOS. (Issue 23496 should also likely take the issue 22980 changes into account for the Android cross-build)

I've added Steve Dower to the nosy list as it would also be good to have a set of triplets defined for Windows. MAL suggested in issue 22980 that it may be worth capturing this ABI compatibility identification discussion as a PEP rather than solely as a set of issues with resulting changes to the documentation, which I think is a reasonable direction to go (even if it's done primarily as an after-the-fact communication of the build identification changes for inclusion in What's New, rather than a gating requirement for actually doing the work).

----------
nosy: +steve.dower

_______________________________________
Python tracker <report at bugs.python.org>
<http://bugs.python.org/issue23966>
_______________________________________