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

[Hausmann Simon]

‎Hi,

Should bootstrap really use the mkspec compiler? I'm not sure that's always the right thing. Bootstrap should just use _any_ compiler.

What is the underlying problem that you are trying to solve?


Simon

  Original Message
From: René J.V. Bertin
Sent: Sunday, March 22, 2015 21:24
To: 'interest at qt-project.org'
Cc: <development at qt-project.org>
Subject: Re: [Development] bug: qmake ignores CMAKE_CC and CMAKE_CXX while      building Qt 5.3.2???


On Sunday March 22 2015 19:01:55 René J.V. Bertin wrote:

I found the immediate culprit: build/qtbase/qmake/.qmake.stash
This file sets QMAKE_MAC_SDK.macx-clang.macosx.QMAKE_CC etc. to values that are completely unrelated to what's specified in the mkspec file. I think that also explains another issue I've had that is also due to the bootstrap qmake ignoring the information from the specified mkspec file.

I have not yet figured out where the .qmake.stash file is generated though (pbuilder_pbx.cpp?) but fortunately it appears to be possible to pre-generate a version with the appropriate values before calling configure.

R.

> Hi,
>
> How come that the bootstrap qmake ignores the mkspec's CMAKE_CC and CMAKE_CXX? I see `/usr/bin/clang++` and `/Developer/usr/bin/clang` (for C and ObjC++) when configure runs the config.test tests, and this causes problems because I need to use the clang compiler specified in my mkspec.
>
> NB: build/qtbase/mkspecs/qmodule.pri does contain the correct compiler paths!
> NB2: the bootstrap qmake in fact ignore the mkspec completely: introducing a syntax error in it doesn't raise an error.
>
> I'm OK with patching the qmake code, but will need to know where ...
>
> Thanks,
> R.

_______________________________________________
Development mailing list
Development at qt-project.org
http://lists.qt-project.org/mailman/listinfo/development