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

[René J.V. Bertin]

On Monday March 23 2015 11:10:06 Thiago Macieira wrote:

> On Monday 23 March 2015 18:42:01 René J.V. Bertin wrote:
> > On Monday March 23 2015 09:33:30 Thiago Macieira wrote:
> > > Ok. What is the target that was being built? The very first thing? That
> > > would be libQtBootstrap.a.
> > 
> > Does it matter what target was being built? 
> 
> Are you sure it doesn't?

I'm sure it doesn't in the case which prompted me to start this thread, yes.

> > 1) This also works:
> > %> tar -xf qt-everywhere*
> > %> rm -rf qt-everywhere*/qtwebengine
> > %> mkdir build ; cd build
> > %> ../qt-everywhere*/configure -platform macx-clang-32
> > %> gmake && sudo make install
> 
> Looks good so far.
> 
> > 2) After 1), this fails (or rather, it builds qtwebengine for 64bit):
> > %> tar -xf qt-everywhere* "qt-everywhere*/qtwebengine"
> > %> mkdir build ; cd build
> > %> qmake -spec macx-clang-32 -r
> > ../qt-everywhere*/qtwebengine/qtwebengine.pro 
> 
> Which qmake was this? The installed one to /usr/local/.... ?

Yes, the one installed in the last step in 1).

> > %> make
> 
> Does that also happen if you don't do this complicated way to separately build 
> qtwebengine?

Is there a less complicated way to build only qtwebengine? If you mean one not using an out-of-source build: yes.

> And note that the target here is EXTREMELY important: qtwebengine has a 
> different buildsystem.

The target in that last make step is whatever the qtwebengine .pro  file defined as the default target. I'm not trying to do anything weird here...

> Then please use a more standard module. Please use qtsvg for this testing. 
> This removes a very complicated variable (the qtwebengine buildsystem).

Ok. That shouldn't be too difficult to arrange.

> > The question is, again, to what extent the 5.3 series are supposed to build
> > on OS X 10.6 ... I was under the impression that they are (were) ...
> 
> It probably does, but again I don't think anyone was testing 32-bit builds.

There's a confusion here: the 32bit build issue is on OS X 10.9 . I only mentioned it in this thread because I believe it's caused by the same underlying cause.

R.