Can not build application msvc2017, Qt 5.10.1, Qt creator 4.8.1

[jsulm]

@Umbaman said in Can not build application msvc2017, Qt 5.10.1, Qt creator 4.8.1:

When installing visual studio professional I just let the visual studio installer to do its job, I didn't change anything.

I think this is the problem. By default C++ part is not installed, you need to select it explicitly.

[Umbaman]

Thank you both for the replies

@aha_1980

2. Windows Defender is used as antivirus

3. This is where all vcvars files are

   C:\Program Files (x86)\Microsoft Visual Studio\2017\Professional\VC\Auxiliary\Build

@jsulm

This is what I have installed

[Umbaman]

Do I need to run vcvars manually?

[aha_1980]

@Umbaman

No, Creator runs it for you. But you can check if you can open a Visual Studio command prompt from the Start Menu. That should exec the same batch file and set up the environment.

Does that work without problems?

[Umbaman]

@aha_1980
Yes It does.!

[Jerry.Wilson]

After line 3 the qmake exited normally, it start the qmake again with "-f" param, I think it should be jom.exe not qmake.exe, qmake has no option "-f", did you change it?

[Umbaman]

@Jerry.Wilson
No I didn't! I don't even know how. I wanted to remove the -f option

[Jerry.Wilson]

@Umbaman
Mmm...as I saw in your picture, you choose qmake.exe as your make tool in the Make Path, I think that is the reason. Qmake is not a make tool, use jom.exe and try again.

[Umbaman]

@Jerry.Wilson hmmm. Something seems to be happening.

This is what I am getting now

C:\Qt\5.10.1\msvc2017_64\include\QtCore/qglobal.h(45): fatal error C1083: Cannot open include file: 'type_traits': No such file or directory

Edit:
this guy here (https://nnarain.github.io/2017/11/10/Config-issues-with-Qt-and-Visual-Studio.html) nailed it!
The corresponding registry key was pointing to the community edition I had, before installing visual studio professional.

I can see a few compilers now autodetected, but not a single kit autoconfigured...
Manually setting a compiler seems to be working but I cannot compile my project correctly.

Example Output

:-1: error: LNK1181: cannot open input file 'debug\main.obj'

[aha_1980]

@Umbaman,

good, it seems we get forward :)

• Can you show your compilers and kits screens again now?
• Can you check if a newly created project compiles?
• If not, please post the complete compile output.

Regards

[Umbaman]

1. Compilers

Kits

2. A new project compiles, runs and can be debugged successfully using the Desktop Kit. I was getting the error mentioned due to white spaces in my path.

As for the UWP kit I get the following output

:-1: warning: winrt_manifest_install.path is not defined: install target not created

therefore nothing happens when I run the project.

[aha_1980]

@Umbaman

Do you need UWP/WinRT? I'm out here, I have never used it...

[Umbaman]

Yes I do.
I need to develop apps for Windows 10 IoT.