[Development] bug: qmake ignores CMAKE_CC and CMAKE_CXX while building Qt 5.3.2???

René J.V. Bertin rjvbertin at gmail.com
Mon Mar 23 10:08:02 CET 2015

On Sunday March 22 2015 23:18:17 Thiago Macieira wrote:

>The point is that we extract QMAKE_CC and QMAKE_CXX from the mkspec so that we 
>can build qmake.

Just to be clear: *my* point is that on OS X those variables are basically ignored during a Qt build.

>The C compiler is usually called "cc", but the C++ compiler has no 
>standardised name. We need the mkspec to know it.


Progress report: using my trick of pre-filling a .qmake.stash file in build/qtbase let the build process continue for hours without a glitch *). Until it hit the -Wno-c++* options used for building QtWebkit; turns out QtWebkit found a way to thwart my mkspec and use an Xcode compiler ...

*) 1 probable bug: one of the geoclue files does `value = new GValue; *value = GVALUE_INIT;`. Apparently that passes Apple's clang and gcc, despite the explicit warning above the GVALUE_INIT macro definition that it cannot be used to initialise variables except when they're being declared. Stock clang-3.5 apparently agrees, so I had to do `memset(value,0,sizeof(GValue))`.

More information about the Development mailing list