Skip to content
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

Wildcards don't work after 1.19.5 update #13101

Closed
jrcody opened this issue Jan 3, 2025 · 4 comments
Closed

Wildcards don't work after 1.19.5 update #13101

jrcody opened this issue Jan 3, 2025 · 4 comments
Assignees
Labels
more info needed The issue report is not actionable in its current state tasks/build/debug An issue relating to tasks.json (e.g. build issues)

Comments

@jrcody
Copy link

jrcody commented Jan 3, 2025

Type: Bug

I've tried rebuilding code I used from spring of 2024 which used wild cards in the tasks.json arg array (e.g., **). I saw that 1.19.4 intentionally disabled wild cards but that 1.19.5 fixed it; however, I'm in the latest version, fresh download/install, and I still can't use them. Is there something I missed? Thanks!

Extension version: 1.22.11
VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT arm64 10.0.26100
Modes:

@sean-mcmanus
Copy link
Contributor

@jrcody We need more info on how ** is used in tasks.json. Where did you see that 1.19.4 intentionally disabled wild cards and that 1.19.5 fixed it? https://github.com/microsoft/vscode-cpptools/releases/tag/v.1.19.4

@sean-mcmanus sean-mcmanus self-assigned this Jan 3, 2025
@sean-mcmanus sean-mcmanus added more info needed The issue report is not actionable in its current state tasks/build/debug An issue relating to tasks.json (e.g. build issues) labels Jan 3, 2025
@jrcody
Copy link
Author

jrcody commented Jan 3, 2025

Thank you for getting back to me so quickly!

I was creating a simple program to open a window (start of a graphics project). It works if I explicitly name the files instead of using the ** you can see in the args array. I can provide more context if needed.

tasks.json example: tasks.json

Attempt and errors:
Starting build...
cmd /c chcp 65001>nul && C:\msys64\ucrt64\bin\g++.exe "C:\Users\Jason Cody\Projects\helloworld*.cpp" "C:\Users\Jason Cody\Projects\helloworld*.c" -IC:\msys64\ucrt64\include -lglfw3 -lgdi32 -lglu32 -lopengl32 -o "C:\Users\Jason Cody\Projects\helloworld\helloworld.exe"
cc1plus.exe: fatal error: C:\Users\Jason Cody\Projects\helloworld*.cpp: Invalid argument
compilation terminated.
cc1plus.exe: fatal error: C:\Users\Jason Cody\Projects\helloworld*
.c: Invalid argument
compilation terminated.

The post I referred to was here (reference v.1.19.4) -- my apologies if I conflated two issues: https://github.com/microsoft/vscode-cpptools/issues/12001

I was trying to use the instructions below while setting up a basic graphics window program (runs fine if I explicitly name the files--but not great for the future when I will need to compile many files).

https://code.visualstudio.com/docs/cpp/config-mingw#_modifying-tasksjson

@benkyllo
Copy link

benkyllo commented Jan 6, 2025

I'm having the same problem, wildcards shown in the example don't work.

Looks like this may be a duplicate ticket here:
#13096

I'd like to know how to enable them in msys2!

@browntarik
Copy link
Contributor

I am going to close this issue as a duplicate. Please follow #13096 for more updates on this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
more info needed The issue report is not actionable in its current state tasks/build/debug An issue relating to tasks.json (e.g. build issues)
Projects
None yet
Development

No branches or pull requests

4 participants