Re: [Development] Cross-compile Qt 4.8.x for QNX 6.5.0

On terça-feira, 19 de dezembro de 2017 14:39:24 PST Jake Petroules wrote: > >> Am I doing something wrong, or is it really so that nobody tested if Qt > >> >= > >> 4.8.5 builds for QNX 6.5 before me? > > > > You are doing something wrong: trying Qt 4.8 for any new project in > > almost-2018.

Re: [Development] Cross-compile Qt 4.8.x for QNX 6.5.0

> On Dec 19, 2017, at 2:28 PM, Thiago Macieira > wrote: > > On terça-feira, 19 de dezembro de 2017 12:44:36 PST Oleg Yadrov wrote: >> Configuration finishes successfully, I run make a get a message >> "qlocale_unix.cpp:36: error: '_CS_LOCALE' was not declared in

Re: [Development] Cross-compile Qt 4.8.x for QNX 6.5.0

On terça-feira, 19 de dezembro de 2017 12:44:36 PST Oleg Yadrov wrote: > Configuration finishes successfully, I run make a get a message > "qlocale_unix.cpp:36: error: '_CS_LOCALE' was not declared in this scope. qlocale_unix.cpp line 36 in Qt 4.8 is a comment:

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

Hi all, I just found out that the build failed while running this command in qtwebengine/src/core: /TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/3rdparty/ninja/ninja -C /TOOLCHAIN/loop/target/nicebox/sandbox/qt-everywhere-src-5.10.0/qtwebengine/src/core/release

[Development] Cross-compile Qt 4.8.x for QNX 6.5.0

Hi, I'm having issues while trying to build Qt 4.8.7 for QNX 6.5.0 (vanilla QNX 6.5.0 without SP1 and libscreen patches installed). Seems like nobody tested if Qt 4.8.5 (I've tried both 4.8.7 and 4.8.5 and observed exactly the same errors) builds for QNX 6.5.0 before release, because it simply

Re: [Development] 32bit linux build of qt5.10.0 w/ webengine

Here is brief update on my 32bit build: 1. 32bit build inside lxc container - code built successfully, qtwebengine worked perfectly. The only problem w/ this one is that it does not use compatible glibc library as my target board. 2. 32bit build inside t2 sandbox - I got the builder to use

Re: [Development] Time to switch to android-clang

On terça-feira, 19 de dezembro de 2017 03:25:17 PST Sergio Martins wrote: > Furthermore, supporting both android and android-clang is a maintenance > burden: the mkspecs are often broken, either because of a new Qt version > or because of a new NDK version. Then you have to test not only gcc and >

[Development] Time to switch to android-clang

Hi all, We need to start offering pre-built android binaries built with android-clang and bump our minimum supported NDK version. gcc on android is pretty much dead since 2016: "GCC is no longer supported. It will be removed in NDK r18. libc++ is now the default STL for CMake and