IntelliSense errors with importing a module on Windows with cl.exe

[sean-mcmanus]

    Ok, some progress:

I've created a new simpler project with one module but this time, I've created from Visual Studio 2022 Community CMake project wizard.

This time Visual Studio has no problem in finding the module (you must compile it twice for it to work properly - because the first time it generates the ifc files):

VSCode still can't see it:

The CMake project uses presets when created with VS wizards.

In both I can compile, run, and debug normally.

And if I force the /ifcSearchDir into CMakeLists.txt VSCode gives me the edgm error (VS does see the modules and finds the ifc files without setting this manually in the CMakeLists.txt). I noticed that .command files were generated in the build destination, and they have all the compilers parameters that are necessary to compile each file. My guess is that VS is using it to correctly generate the Intellisense and find everything.

Originally posted by @Bigous in #6302 (comment)

[JG-Adams]

Any idea when they'll fix this?
I use VScode Cmake Mingw.
And I get this importing error. But, I can compile the program just fine.
I just don't want to have to deal with a bunch of red lines all over the place making it difficult to find the real issue.
If I can have a way to simply remove those particular issue that would be helpful.

[wzhengsen]

@sean-mcmanus Hi, this issue has been around for a year, has it been resolved so far?

[sean-mcmanus]

@JG-Adams Your issue is #6302 . This issue is just for the cl.exe case.

@wzhengsen Are you using cl.exe or gcc/clang?

[wzhengsen]

@sean-mcmanus I use VScode, Cmake, cl.exe