Your browser does not seem to support JavaScript. As a result, your viewing experience will be diminished, and you have been placed in read-only mode.

Please download a browser that supports JavaScript, or enable it if it's disabled (i.e. NoScript).

Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory

Solved Qt Creator and other tools

5 Posts 3 Posters 2.2k Views

M Offline
M Offline
MikhailG

wrote on 16 Dec 2019, 20:53 last edited by MikhailG

#1
Hello! Trying to build qt creator (the last available version on github) from source but having this compilation error :
c:\qt-creator\source\src\shared\qbs\src\shared\qtscript\src\3rdparty\javascriptcore\javascriptcore\wtf\Assertions.h(48): fatal error C1083: Cannot open include file: 'stddef.h': No such file or directory
Qt version: Qt 5.13.1 msvc2017 (32bit)
MSVC Vesroin: MSVC 2017 14.16.27023

Environment variables Path:
C:\Program Files (x86)\Windows Kits\10\Include\10.0.18362.0\ucrt
C:\Program Files (x86)\Windows Kits\10\Include\10.0.17763.0\ucrt
C:\Program Files (x86)\Windows Kits\10\Include\10.0.10240.0\ucrt

Allso I have 2019 VS installed, Qt 5.13.1 msvc2017 (64bit). But error keep happening. I REALLY do not want to reinstall everything from scratch. Maybe I miss something?
1 Reply Last reply

0
C Offline
C Offline
Christian Ehrlicher
Lifetime Qt Champion
wrote on 17 Dec 2019, 06:55 last edited by

#2

I would say the Windows SDK is missing. What exact compiler do you use (cl /?) and do you really opened a visual studio command prompt?
Qt Online Installer direct download: https://download.qt.io/official_releases/online_installers/
Visit the Qt Academy at https://academy.qt.io/catalog
M 2 Replies Last reply 17 Dec 2019, 09:50

2
C Christian Ehrlicher
17 Dec 2019, 06:55

I would say the Windows SDK is missing. What exact compiler do you use (cl /?) and do you really opened a visual studio command prompt?
M Offline
M Offline
MikhailG

wrote on 17 Dec 2019, 09:50 last edited by MikhailG

#3

@Christian-Ehrlicher Is Some specific SDK or in general it is missing? As for

@Christian-Ehrlicher said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory:

and do you really opened a visual studio command prompt?

No, I was trying to built using Qt command prompt. Will try to build using VS command promt.

@Christian-Ehrlicher said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory:

What exact compiler do you use (cl /?)

cl.
A 1 Reply Last reply 17 Dec 2019, 10:30

0
M MikhailG
17 Dec 2019, 09:50

@Christian-Ehrlicher Is Some specific SDK or in general it is missing? As for

@Christian-Ehrlicher said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory:

and do you really opened a visual studio command prompt?

No, I was trying to built using Qt command prompt. Will try to build using VS command promt.

@Christian-Ehrlicher said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory:

What exact compiler do you use (cl /?)

cl.
A Offline
A Offline
aha_1980
Lifetime Qt Champion
wrote on 17 Dec 2019, 10:30 last edited by

#4

@MikhailG said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory:

cl.

And the version? @Christian-Ehrlicher meant to call cl /? in the command window...

Regards
Qt has to stay free or it will die.
1 Reply Last reply

1
C Christian Ehrlicher
17 Dec 2019, 06:55

I would say the Windows SDK is missing. What exact compiler do you use (cl /?) and do you really opened a visual studio command prompt?
M Offline
M Offline
MikhailG

wrote on 17 Dec 2019, 19:21 last edited by

#5

@Christian-Ehrlicher said in Trying to build qt creator from source with MSVC: Cannot open include file: 'stddef.h': No such file or directory:

and do you really opened a visual studio command prompt

Thank you that was it! Wrong command prompt.
1 Reply Last reply

0

1/5

16 Dec 2019, 20:53