No wildcards on Windows CMD.EXE #341
Labels
No labels
announcement
bug
build
CI
dependencies
documentation
duplicate
enhancement
experience feedback
feature request
github_actions
help wanted
install
invalid
Long-term
optimization
portability
question
target-specific
test issue
wontfix
No milestone
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
gh-Cyan4973/xxHash#341
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Hooray, another Windows bug.
The current
GetCommandLineWmethod does not expand wildcards oncmd.exe:v0.7.2:
v0.7.3:
Note that this is not a problem with
wmain.I think the solution is to use
__wgetmainargswith_DoWildCard = 1.This also avoids linking against
shell32.dll, which is a lot of bloat:CommandLineToArgvW:__wgetmainargs:I still need to do more research, but this seems to work great on classic MinGW, even skipping the borked shell globbing (still doesn't support typing the filename):
__wgetmainargsworks on XP. Will open a PR once I clean things up.I presume this issue has been fixed by one of your patches @easyaspi314 ?
For information, I had the same issue a long time ago, while working on
lz4on Visual Studio.It was solved by adding a link dependency in the builder, something like
setargv.obj. It worked well, requiring no change of code, though the dependency was specified in, and therefore only enabled from, the Visual Studio script.Hmm. They really make it confusing
Either way, AFAICT everything is working.
Err…
0.7.3 was released before this patch.