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

> On 20 Dec 2017, at 19:28, Thiago Macieira wrote: > > On quarta-feira, 20 de dezembro de 2017 09:42:39 PST Lars Knoll wrote: >>> I still call a mistake to use Qt 4.8 for ANY new project in 2018. Whether >>> KDAB or ICS or TQtC actually makes money off other people's

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

On quarta-feira, 20 de dezembro de 2017 09:42:39 PST Lars Knoll wrote: > > I still call a mistake to use Qt 4.8 for ANY new project in 2018. Whether > > KDAB or ICS or TQtC actually makes money off other people's mistakes is > > totally orthogonal. Just don't be jack^*&*es and do advise your

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

> On 20 Dec 2017, at 00:13, Thiago Macieira wrote: > > 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? No, at least

Re: [Development] Dropping of MSVC 2013

On quarta-feira, 20 de dezembro de 2017 06:49:40 PST Ville Voutilainen wrote: > Sounds good, +1, good riddance. +1 With the drop of QNX 6.6, we'll finally be C++11 core language feature- complete, only ~7 years after it came out. Fortunately, those numbers seem to be coming down. We should be

[Development] Weird issue in CI

I'm repeatedly getting this error: Failed to provision template 'qtci-linux-Ubuntu-16.04-x86_64-1-b46ac1': Failed repeatedly to launch build/test agent Details: https://testresults.qt.io/coin/integration/qt/qtwebkit/tasks/1513784851 No log exist. -- Regards, Konstantin

Re: [Development] Proposal to remove QNX 6.6 support from Qt 5.11 onwards

On fredag 15. desember 2017 20.04.33 CET Tuukka Turunen wrote: > Hi, > > > I propose to remove support for QNX 6.6 from Qt 5.11 onwards. Yes please, it has been a bit of a trouble maker every once in a while :) For example not needing to patch a header file on the platform is a good thing.

Re: [Development] Dropping of MSVC 2013

On 20 December 2017 at 16:17, Lars Knoll wrote: > Hi all, > > here are the promised numbers: > *Version* > *Compiler* > *Commercial* > > *Version* > *Compiler* > *Opensource* > 5.10.0 > MinGW530 > 22 % > > 5.10.0 > MinGW530 > 25 % > 5.10.0 > MSVC2013_64 > 14 % > > 5.10.0 >

Re: [Development] Dropping of MSVC 2013

Hi all, here are the promised numbers: Version Compiler Commercial Version Compiler Opensource 5.10.0 MinGW530 22 % 5.10.0 MinGW530 25 % 5.10.0 MSVC2013_64 14 % 5.10.0 MSVC2013_64 15 % 5.10.0 MSVC2015 20 % 5.10.0 MSVC2015 18 % 5.10.0 MSVC2015_64 20 % 5.10.0 MSVC2015_64

Re: [Development] [Android] Use pkg-config to link with external libraries in qmake project

Ohhh.. exactly, many thanks... :) 20.12.2017 13:53, Oswald Buddenhagen пишет: On Wed, Dec 20, 2017 at 01:03:30PM +0300, Denis Shienkov wrote: c:/Android/gstreamer/armv7c:/Android/gstreamer/armv7/include/gstreamer-1.0 i really wouldn't expect this to work. ;) the problems seems to be

Re: [Development] [Android] Use pkg-config to link with external libraries in qmake project

On Wed, Dec 20, 2017 at 01:03:30PM +0300, Denis Shienkov wrote: >c:/Android/gstreamer/armv7c:/Android/gstreamer/armv7/include/gstreamer-1.0 > i really wouldn't expect this to work. ;) the problems seems to be that pkg-config outputs the paths in a format that cannot be possibly understood by

Re: [Development] [Android] Use pkg-config to link with external libraries in qmake project

Next, I have modified the link_pkgconfig.prf to add there a message output like: ... INCLUDEPATH *= $$PKGCONFIG_INCLUDEPATH DEFINES *= $$PKGCONFIG_DEFINES message("bla $$INCLUDEPATH") ... and I see required output: Project MESSAGE: bla

Re: [Development] [Android] Use pkg-config to link with external libraries in qmake project

I even have tried following from the Windows cmd durectly: set PATH=c:\pkgconfig\bin;%PATH% set PKG_CONFIG_LIBDIR=c:/Android/gstreamer/armv7/lib/pkgconfig set PKG_CONFIG_SYSROOT_DIR=c:/Android/gstreamer/armv7 pkg-config.exe --cflags gstreamer-1.0 Output is: -pthread

Re: [Development] [Android] Use pkg-config to link with external libraries in qmake project

Hi Oswald, Hmm.. many thanks for your hint, I have modified the pkg-conf env variables to: 1. PKG_CONFIG_LIBDIR = c:\Android\gstreamer\armv7\lib\pkgconfig  - a path to all *.pc files. 2. PKG_CONFIG_SYSROOT_DIR = c:\Android\gstreamer\armv7  - a path to a 'fake' sysroot, which contains an

Re: [Development] [Android] Use pkg-config to link with external libraries in qmake project

On Wed, Dec 20, 2017 at 11:39:20AM +0300, Denis Shienkov wrote: > This says about the 'sysroot', but, I have no any sysroot for Android kit, > that's just implausible. you must have something that resembles a sysroot, even if it's not declared as such. if you don't find anything else, just use

[Development] [Android] Use pkg-config to link with external libraries in qmake project

Hi all, is it possible to use the pkg-config to build the Android's applications? e.g. I want to use the GStreamer for the Android application, using the pkg-config. I already have installed & configured the the Android Kit, have downloaded the Gstreamer SDK for ARMv7 platform. I use the

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

On marți, 19 decembrie 2017 11:25:17 EET Sergio Martins wrote: [...] > > The problem of clang generating bigger binaries was much improved with > -Oz, now size increase is only 10%. > Which, on ARM, usually means the bins are slower ;-) [...] Anyway, a +0.5 also from my side. Cheers, BogDan.