Roger Chaplin <[EMAIL PROTECTED]> wrote:
> If that is indeed the case, then it all boils down to which shell is
> executing the command. If your shell does globbing, it works. If it
> doesn't do globbing, the command fails.
Right.
Now I get it. The big problem is that you guys are using Windows 95, right?!
On Windows NT without MAKE_MODE you get cmd.exe, which will glob like this:
* build-prc pilrctst.prc "pilrc test" plRc pilrctst *.bin
Quoted spaces like the one in `"pilrc test"' won't get quoted. So this
doesn't work.
* build-prc pilrctst.prc "pilrc-test" plRc pilrctst *.bin
This one works just fine. But the quotes seem redundant now...
* build-prc pilrctst.prc pilrc-test plRc pilrctst *.bin
Now *.bin doesn't get globbed! It seems that you need some quotes on the
command line somewhere -- anywhere, even `"*.bin"' will do -- in order to
get cmd.exe to glob filenames somewhere else on the command line. (?!)
On Windows 95 without MAKE_MODE you get command.com, which won't glob at
all when spawned by make. If I do anything with quotes or `*'s I just get
Bad command or filename
Huh!!?!!!! But it works fine when *I* type it on the command line, just
not when spawned by make.
So basically it's completely broken, and everybody MUST use MAKE_MODE on
Windows. I don't understand how programmers forced to use Windows have
any hair left...
Okay, so clearly the installer needs to say something very loud about
all this...
John "get yourselves a *real* operating system! :-)"
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
