Anyone?
This is still happening.
If we don't know how to fix this, I propose we make the iOS builds force-pass
all tests.
On Thursday 19 March 2015 13:43:43 Thiago Macieira wrote:
> This has been happening for a while. Someone who knows about iOS, please
> talk to the QA team to make sure this
On Monday 23 March 2015 05:46:47 Hausmann Simon wrote:
> I think we are talking about the compiler that is used to build qmake here,
> not the tools. I agree that -platform should be used for the tools, but for
> qmake itself IMO any compiler should suffice and not require parsing of the
> platform
Hi,
I think we are talking about the compiler that is used to build qmake here, not
the tools. I agree that -platform should be used for the tools, but for qmake
itself IMO any compiler should suffice and not require parsing of the platform
qmake spec (yes, we have some awk hacks in configure t
On Sunday 22 March 2015 20:33:53 Hausmann Simon wrote:
> Should bootstrap really use the mkspec compiler?
Yes, that's what the -platform option is for. The target compiler is specified
by -xplatform.
--
Thiago Macieira - thiago.macieira (AT) intel.com
Software Architect - Intel Open Source Tec
On Sunday March 22 2015 21:35:47 Samir Aguiar wrote:
> I remember that somewhere during the makefile generation qmake runs
> xcrun --find clang
> and uses the output as the compiler path, ignoring what you set in
> QMAKE_CXX.
Yes, that's in qtbase/configure, and it basically determines the compil
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: 'inte
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
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:
