From: Wu Y. <ad...@ne...> - 2005-03-24 04:40:51
|
It is not related with MSYS or bash. The `glob' is really done by the MinGW runtime. To inhibit this behaviour, you need a command line like the following (adjust the path if your MinGW installtion is not in C:\mingw): gcc test.c C:\mingw\lib\CRT_noglob.o Best regards, Yongwei Earl Kinmonth <eh...@go...> To: min...@li... CC: Subject: [Mingw-users] command line wildcard expansion Does the bash shell supplied with MSYS treat native (supplied) MINGW programmes differently from those compiled with the MINGW environment? For example, when I run one of my own programmes compiled under the MINGW environment, the bash shell seems to ignore single quotes. myprog.exe '*.h' gets an expanded version of *.h if there are files by that name in the current directory. In contrast, native programmes get *.h without any expansion because of the single quotes. The other alternative I can think of is that some kind of helpful (like a rubber crutch) initialization route is taking the *.h passed by bash and expanding it for me on the assumption that I'm running from something completely brain dead (command.com) or almost brain dead (cmd.exe). Whichever the case, what do I do to get what I want - '*.h' (single quote, asterisk, dot, h, single quote) leads to my programme seeing *.h (asterisk, dot, h)? EHK |