Do you have a question about makefiles, a compiler or IDE you are using and need to know how to set it up for wxWidgets or why it doesn't compile but other IDE's do ? Post your questions here.
You should fix your include paths so that they do not have the msvc folder with the MSVC-specific setup in it. As the name implies, that setup is not for GCC but for MSVC, where it tries to include the build-specific setup.h from MSVC-built library.
PB wrote: ↑Wed Mar 29, 2023 5:16 am
You should fix your include paths so that they do not have the msvc folder with the MSVC-specific setup in it. As the name implies, that setup is not for GCC but for MSVC, where it tries to include the build-specific setup.h from MSVC-built library.
Why vscode tries to include MSVC-built library? How to force the vscode to include gcc library?
I am not familiar with VSCode JSON syntax but it seems you add to the compiler include paths all the folders in WXWIN/include folder, which has folders msvc and wx.
When your compiler tries to find setup.h, it finds one in WXWIN/include/msvc, which of course, being MSVC-specific setup.h, tries to include the MSVC build-specific setup.h, which does not exist.
Once again, fix your build setup so that your include paths do not end containing WXWIN/include/msvc. Perhaps by removing those trailing asterisks?
PB wrote: ↑Wed Mar 29, 2023 8:39 am
Please read my answer again.
I am not familiar with VSCode JSON syntax but it seems you add to the compiler include paths all the folders in WXWIN/include folder, which has folders msvc and wx.
When your compiler tries to find setup.h, it finds one in WXWIN/include/msvc, which of course, being MSVC-specific setup.h, tries to include the MSVC build-specific setup.h, which does not exist.
Once again, fix your build setup so that your include paths do not end containing WXWIN/include/msvc. Perhaps by removing those trailing asterisks?