Re: [Development] Urgent help needed: determining endianness at compile time in INTEGRITY
> So they are defined but not required to be equal to something? Yup, that's right Regards, Kimmo Ollila -Original Message- From: Development <development-bounces+kimmo.ollila=qt...@qt-project.org> On Behalf Of Thiago Macieira Sent: torstaina 17. toukokuuta 2018 9.47 To: development@qt-project.org Subject: Re: [Development] Urgent 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 order. > > __LITTLE_ENDIAN__ > Little Endian byte order. So they are defined but not required to be equal to something? Ok, will change the change. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
Re: [Development] Urgent help needed: determining endianness at compile time in INTEGRITY
Hi, >From INTEGRITY documentation I found the following macros: 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. I tested and these are working. Best regards, Kimmo Ollila -Original Message- From: Development <development-bounces+kimmo.ollila=qt...@qt-project.org> 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 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 test program in C that shows how to determine the endianness at compile time (c) a function that does 64-bit host-to-network and back conversions on INTEGRITY (d) an actual patch to TinyCBOR - https://github.com/intel/tinycbor (file src/compilersupport_p.h) Please note that Qt doesn't seem to have a problem -- qprocessordetection.h has an #error and it's not triggering. So it would seem Qt has a solution. I have not looked at the code because I need to submit to the third-party and I need therefore MIT-licensed solutions. A Qt Company employee could open qprocessordetection.h and determine how it makes this work -- the only other copyright holder of relevance in that file is Intel. For reference, TinyCBOR already tries these tests: __BYTE_ORDER__ == __ORDER_BIG_ENDIAN__ __BYTE_ORDER == __BIG_ENDIAN BYTE_ORDER == BIG_ENDIAN defined(__ARMEB__) || defined(__MIPSEB__) || defined(__sparc__) __BYTE_ORDER__ == __ORDER_LITTLE_ENDIAN__ __BYTE_ORDER == __LITTLE_ENDIAN BYTE_ORDER == LITTLE_ENDIAN defined(__ARMEL__) || defined(__i386) || defined(__i386__) || defined(__x86_64) || defined(__x86_64__) || \ defined(__amd64) || defined(__MIPSEL__) It's possible it's one of those and there's something else wrong. I don't have access to the toolchain and therefore can't test to see what it is. -- Thiago Macieira - thiago.macieira (AT) intel.com Software Architect - Intel Open Source Technology Center ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
[Development] Boot2Qt Device Utilities module repo
Hi All, We are planning to open new Boot2Qt Device Utilities module repository. Qt Device Utilities module allows user manipulate easily various embedded device settings via simple QML APIs. More information can be found at the end of the blog post below: https://blog.qt.io/blog/2016/06/16/qt-5-7-for-device-creation/ I also want to propose Teemu Holappa to be the maintainer of Boot2Qt Device Utilities since he is the one who implemented the module. Br, Kimmo Ollila The Qt Company Email: kimmo.oll...@qt.io<mailto:kimmo.oll...@qt.io> Mobile: + 358 50 590 9774 http://qt.io -- PRIVACY AND CONFIDENTIALITY NOTICE This message and any attachments are intended only for use by the named addressee and may contain privileged and/or confidential information. If you are not the named addressee you should not disseminate, copy or take any action in reliance on it. If you have received this message in error, please contact the sender immediately and delete the message and any attachments accompanying it. Digia Plc does not accept liability for any corruption, interception, amendment, tampering or viruses occurring to this message. - ___ Development mailing list Development@qt-project.org http://lists.qt-project.org/mailman/listinfo/development
