Qt app build from command line

[sayan275]

Am trying to build a qt app from cmd line, but facing the same issue after all steps of adding to env var PATH and running the qtenv2 and vcvarsall bat in admin mode.

another way and even tried with jom.exe

setting up env with admin rights

[sierdzio]

To reiterate: you have to run vcvarsall.bat in the same session you run qmake. That means the same cmd.exe window, same execution rights (not admin!). When you close session (close window or type exit), your build environment will be forgotten. This is so by design.

m trying to find the v15.x specific bat and exe to build.

Exact path is printed in your 3rd screenshot.

[sierdzio]

Is your visual studio up to date?

[ChrisW67]

Please confirm you setup the command prompt in the bottom screen shot and then ran the build in the top screen shot from the same command prompt. These observations cast some doubt here:

• The text is different colours in the bottom versus build command prompts
• The environment setup lists version VS2017 v15.9.12. The nmake utility is reporting v14.16.27013.1. Visual Studio 2015 would be V14.x;

[sayan275]

MS Visual Studio 2017 pro version installed.
I haven't done any update after the installation. With current version am able to build by Qt creator perfectly fine.

[sierdzio]

As @ChrisW67 mentioned, your first 2 screenshots suggest the terminal is actually using MSVC 2015, which is too old.

Make sure you run vcvarsall.bat from MSVS 2017 in the same terminal session where you want to compile.

[sayan275]

@ChrisW67 yes...seems an issue, am trying to find the v15.x specific bat and exe to build.
And am updating the VS to MSVC 15.9.38.

[sayan275]

jom.exe is also not able to build as cl.exe is not able to be found.....

[sierdzio]

To reiterate: you have to run vcvarsall.bat in the same session you run qmake. That means the same cmd.exe window, same execution rights (not admin!). When you close session (close window or type exit), your build environment will be forgotten. This is so by design.

m trying to find the v15.x specific bat and exe to build.

Exact path is printed in your 3rd screenshot.

[sayan275]

@sierdzio ok I'll do an exit at end to close and to try to build.
Some issue vs version installed in my system. Am not find the folder with v15.9.XXX
C:\LegacyApp\Microsoft Visual Studio\VC\Tools\MSVC\14.16.27023\bin\Hostx64\x64\nmake,exe
C:\LegacyApp\Microsoft Visual Studio\VC\Auxiliary\Build\vcvarsall.bat

These are added in ENV var PATH.

another nmake I found in this location.
C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\bin

[sierdzio]

@sayan275 said in Qt app build from command line:

@sierdzio ok I'll do an exit at end to close and to try to build.

?? I've told you to do the exact opposite. Anyway, just try it out.

Some issue vs version installed in my system. Am not find the folder with v15.9.XXX

But the screenshot clearly shows VS 15.9.12 residing in: C:\LegacyApp\Microsoft Visual Studio\VC\Auxiliary\Build

[sayan275]

@sierdzio said in Qt app build from command line:

15.9.12 r
Thank you all.

Yes tried all in same console and it worked.

But not able understand the version difference with folders and what's getting on console.

[sierdzio]

@sayan275 said in Qt app build from command line:

Yes tried all in same console and it worked.

Nice!

But not able understand the version difference with folders and what's getting on console.

You mean that it sometimes loads VS 2015 and sometimes 2017? Yeah that's pretty weird. You'll need to search through your disk to find real concrete paths to both of your compilers.

[ChrisW67]

If the VS 2015 executables are in the default system PATH then this is the result I would expect from a normal CMD shell. I expect that after running vcvarsall in that CMD shell its PATH will have the VS 2017 binary directory inserted before the VS 2015 ones.