-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The wildcard can't be used by the C/C++ compiler recommanded! #13096
Comments
Could you provide more information about this compiler you are using? What is the exact path of "g++" in the command line? Does this repro when you use the full path to the ucrt version of the compiler (i.e "C:/msys64/ucrt64/bin/g++.exe") in the command line? Does the issue reproduce without using the cppbuild task and just the command line? |
Yes, g++ means D:\msys64\ucrt64\bin\g++.exe which is downloaded by msys2 that vscode document recommended. |
If the issue reproduces when you just use the command line, then the issue may have to do with your shell and not our extension. I am not able to reproduce your behavior using the same compiler. It wasn't clear based on your response if you have tried compiling with the full path. Can you confirm that doesn't work? Did you ensure the ucrt compiler was added to your PATH environment variable? |
This issue is about documentation rather than cpptools itself. Maybe https://github.com/microsoft/vscode-docs/issues is the better place to report it. https://code.visualstudio.com/docs/cpp/config-mingw recommends using gcc from msys2, which was not configured with However gcc from winlibs is configured with |
When I browsed the doc of GCC on Windows,I found that I could modify my tasks.json file to build multiple C++ files by using an argument like "${workspaceFolder}/*.cpp" instead of "${file}". But there is a fatal error when I run my program. The information is that *.cpp is invalid argument.
What is interesting is that my program runs sucessfully if I use another compiler downloaded from https://winlibs.com/.
The text was updated successfully, but these errors were encountered: