Skip to content
  • Categories
  • Recent
  • Tags
  • Popular
  • Users
  • Groups
  • Search
  • Get Qt Extensions
  • Unsolved
Collapse
Brand Logo
  1. Home
  2. Qt Development
  3. Installation and Deployment
  4. cannot open source file, std lib files
Forum Updated to NodeBB v4.3 + New Features

cannot open source file, std lib files

Scheduled Pinned Locked Moved Solved Installation and Deployment
2 Posts 1 Posters 1.6k Views 1 Watching
  • Oldest to Newest
  • Newest to Oldest
  • Most Votes
Reply
  • Reply as topic
Log in to reply
This topic has been deleted. Only users with topic management privileges can see it.
  • M Offline
    M Offline
    MattyJacques
    wrote on 3 Aug 2017, 13:44 last edited by
    #1

    I'm trying to get Qt up and running on Visual Studio 2017 but I can't seem to build the project.

    Windows 10
    Visual Studio 2017

    Installed Qt via the online installer selecting msvc2017 version. I added "msvc2017_86\bin" to environment variables. However I'm still getting these errors messages.

    This is the output and the error list states lines like

    Error (active)	E1696	cannot open source file "stddef.h"	TestProject   	c:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\include\atomic	15	
    
    1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\include\crtdefs.h(10): fatal error C1083: Cannot open include file: 'corecrt.h': No such file or directory
    1>moc_BacklogManager.cpp
    1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\include\crtdefs.h(10): fatal error C1083: Cannot open include file: 'corecrt.h': No such file or directory
    1>main.cpp
    1>C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.10.25017\include\crtdefs.h(10): fatal error C1083: Cannot open include file: 'corecrt.h': No such file or directory
    
    1 Reply Last reply
    0
    • M Offline
      M Offline
      MattyJacques
      wrote on 3 Aug 2017, 15:16 last edited by
      #2

      Turns out this way due to me editing the Visual Studio 2017 install. For some reason I must have unchecked "Standard Library Modules" during in install. What an idiot.

      1 Reply Last reply
      0

      1/2

      3 Aug 2017, 13:44

      • Login

      • Login or register to search.
      1 out of 2
      • First post
        1/2
        Last post
      0
      • Categories
      • Recent
      • Tags
      • Popular
      • Users
      • Groups
      • Search
      • Get Qt Extensions
      • Unsolved