Re: [Development] Urgent help needed: determining endianness at compile time in INTEGRITY

2018-05-16 Thread Kimmo Ollila
ent help needed: determining endianness at compile time in INTEGRITY On Wednesday, 16 May 2018 23:26:27 PDT Kimmo Ollila wrote: > Endianness Macros > One of these symbols is always defined to specify the endianness of > the target processor. > > __BIG_ENDIAN__ > Big Endian byte ord

Re: [Development] Urgent help needed: determining endianness at compile time in INTEGRITY

2018-05-16 Thread Thiago Macieira
On Wednesday, 16 May 2018 23:26:27 PDT Kimmo Ollila wrote: > Endianness Macros > One of these symbols is always defined to specify the endianness of the > target processor. > > __BIG_ENDIAN__ > Big Endian byte order. > > __LITTLE_ENDIAN__ > Little Endian byte order. So they are defined but not r

Re: [Development] Urgent help needed: determining endianness at compile time in INTEGRITY

2018-05-16 Thread Kimmo Ollila
est regards, Kimmo Ollila -Original Message- From: Development On Behalf Of Thiago Macieira Sent: keskiviikkona 16. toukokuuta 2018 19.19 To: development@qt-project.org Subject: [Development] Urgent help needed: determining endianness at compile time in INTEGRITY We've got a change

[Development] Urgent help needed: determining endianness at compile time in INTEGRITY

2018-05-16 Thread Thiago Macieira
We've got a change blocked because some third-party code is unable to find a macro that determines the endianness of the target while compiling with GHS's compiler for INTEGRITY. Can someone help? Any of the following would help: (a) documentation link stating what macro is set (b) a simple te