Remove Q_BYTE_ORDER and -*-endian arguments from configures
authorBradley T. Hughes <bradley.hughes@nokia.com>
Fri, 24 Feb 2012 10:11:02 +0000 (11:11 +0100)
committerQt by Nokia <qt-info@nokia.com>
Fri, 2 Mar 2012 13:48:00 +0000 (14:48 +0100)
commit17ddce4692b31af4374b28cd40b9f25e8ed629cd
tree773832a8b53104941f5a9744535e41c5f68858f6
parent62a654cc902197cc99326879076ba53b6509dc67
Remove Q_BYTE_ORDER and -*-endian arguments from configures

Do not write Q_BYTE_ORDER to qconfig.h in the configures. Instead,
we #define Q_BYTE_ORDER in qprocessordetection.h, since many CPUs only
support a single endian format. For bi-endian processors, we set
Q_BYTE_ORDER depending on how the preprocessor sets __BYTE_ORDER__,
__BIG_ENDIAN__, or __LITTLE_ENDIAN__ (instead of using a compile test
to do so).

For operating systems that only support a single byte order, we can
check for Q_OS_* in addition to the preprocessor macros above. This is
possible because qprocessordetection.h is included by qglobal.h after
Q_OS_* and Q_CC_* detection has been done. Do this for Windows CE,
which is always little- endian according to MSDN.

Change-Id: I019a95e05252ef69895c4b38fbfa6ebfb6a943cd
Reviewed-by: Oswald Buddenhagen <oswald.buddenhagen@nokia.com>
config.tests/unix/endian.test [deleted file]
config.tests/unix/endian/endiantest.cpp [deleted file]
config.tests/unix/endian/endiantest.pro [deleted file]
configure
configure.bat
src/corelib/global/qprocessordetection.h
tools/configure/configureapp.cpp