[Interest] Is there a command line call to qmake to test the bit width?

[Scott Aron Bloom]

-----Original Message-----
From: interest-bounces+scott.bloom=onshorecs.com at qt-project.org [mailto:interest-bounces+scott.bloom=onshorecs.com at qt-project.org] On Behalf Of Thiago Macieira
Sent: Wednesday, March 04, 2015 9:44 AM
To: interest at qt-project.org
Subject: Re: [Interest] Is there a command line call to qmake to test the bit width?

On Wednesday 04 March 2015 17:15:45 Scott Aron Bloom wrote:
> By then its too late.. I want the shell script that calls the make 
> system to fail, saying you have the qmake setup wrong...

Why would it be wrong? If qmake is installed, it's been installed correctly right? :-)

And what is the issue you're trying to figure out?

> Its really only an issue when linking, since it will pick up the wrong 
> libraries.

No, it won't. The libraries come from the linker.

--

No.  Maybe Im not explaining myself correctly.  Since this was purely a question on qmake, or if there was anyway to look at a Qt install an see what bit width it was built against.

However here are all the gory details.

On a single system, I have 2 versions of the SAME Qt installed, 64 bit and 32 bit, both installed correctly.

Visual Studio has two compilers, one for 64 and one for 32.  That said, when I used to release our tool for linux 32, we had a similar issue..

The developers setup build script, requires the "cl" to be pointing to the correct cl, ie, that you have run vsvars before you run cmake (which then has the dependency on qmake)

If I am trying to build the 64 bit system, but my shell is pointing to the 32 bit compiler, but the 64 bit Qt system, it will most likely compile just fine, but it will not link correctly. 

Im trying to put the logic into my CMake system, to query the version of qmake to determine, if the user has selected the appropriate Visual Studio and Qt version.

And yes, I would have had to do the same thing (though we dropped 32 bit linux support, and devs never really worked on it) to confirm they were building a 32 bit version of the tool against  a 32 bit version of Qt (or vice versa)

Scott