g++ not compiling with wildcard filenames on Windows

Question

All of a sudden I seem to be struggling with compiling c++ programs (specifically TDM64 5.1.0) from the command-line on Windows (specifically 10) when using wildcard based filenames. It works fine when the names are given in full. I've done this countless times before with no problem Edit: But not normally on windows... my memories of this working before must be false. What am I missing?

C:\Users\Duncan Coulter\Code>dir *.cpp
 Volume in drive C has no label.
 Volume Serial Number is 9EE6-DBBD

 Directory of C:\Users\Duncan Coulter\Code

2016/04/04  01:35 PM             7 869 LittleMan.cpp
2016/04/04  01:35 PM             1 912 main.cpp
               2 File(s)          9 781 bytes
               0 Dir(s)  90 288 394 240 bytes free

C:\Users\Duncan Coulter\Code>g++ *.cpp
g++: error: *.cpp: Invalid argument

C:\Users\Duncan Coulter\Code>g++ main.cpp LittleMan.cpp

Please don't post screen shots: You could have written that as quoted plain text (start each line with ">" and five spaces), and it would have been *much* more readable) — Martin Bonner supports Monica, Apr 11 '16 at 11:10
@MartinBonner Ok I've switched it over to plain text as requested. — DuncanACoulter, Apr 11 '16 at 11:52
I don't think it's a memory failure on your part. I just upgraded versions of GCC (current version 4.9.2) and I'm having to change a Windows batch file that used *.cpp successfully before and now fails to work unless I replace that with specific filenames. — Daniel R. Collins, Sep 14 '16 at 03:31

score 5 · Accepted Answer · edited Mar 20 '17 at 10:04

5

Your problem is where you write:

g++ *.cpp

g++ is a linux style program, and expects the shell to expand wildcards for it. The windows command shell doesn't do that - it expects individual programs to expand wildcards for themselves.

The easiest solution is to download cygwin - which does expand wildcards for you. Otherwise the answers to this question may be useful:

https://superuser.com/questions/460598/is-there-any-way-to-get-the-windows-cmd-shell-to-expand-wildcard-paths

edited Mar 20 '17 at 10:04

Community

1
1

answered Apr 11 '16 at 11:09

Martin Bonner supports Monica

28,528
3
51
88

Ah I see I normally use Linux and must have created false memories of this working on windows – DuncanACoulter Apr 11 '16 at 11:53
I presume that MSYS also handles this for me... this would explain why I swear it was working earlier. – DuncanACoulter Apr 11 '16 at 11:57

score 2 · Answer 2 · answered Sep 16 '16 at 22:09

I note that TDM is based on the MINGW port of GCC. I've found that different versions of this compiler do in fact treat the wildcard differently. For example, it works perfectly fine for me as of version 3.4.2, compiling in Windows 7:

However, when I upgraded to GCC v.4.9.2, this batch file and others I was using broke (specifically, the *.cpp was not recognized). This was a version of MINGW GCC which came with the Dev-C++ IDE. Because I needed this feature rather badly (specifically, test-compiling large submissions of student code with unspecified random filenames), I actually had to downgrade and revert back to the old version for just this purpose.

`g++ *.cpp` works perfectly fine for me with mingw-w64 (mingw-builds edition 4.9.2) in windows 10 command prompt — M.M, Sep 16 '16 at 23:04
For what its worth I was also compiling student submissions with unknown file names. — DuncanACoulter, Dec 15 '16 at 05:43

g++ not compiling with wildcard filenames on Windows

2 Answers2