From: Phil C. <fa...@as...> - 2004-09-15 12:54:18
|
On Wed, 15 Sep 2004, Brian Gladman wrote: > > That does sound like a NASM bug, as that is the "correct" way to ensure > > that the space character isn't interpreted by the shell as an IFS. > > As every character apart from '/' and '\0' is valid in a filename, and '/' > > is valid in paths, the only non-permitted character in a -I switch should > > be '\0'. And as we're in C, that's how our argv's will be terminated > > anyway - i.e. NASM should do no processing at all on the rest of the -I > > string at all. > > To be fair to NASM, I have not looked into why the VC++ macro for the > input path fails. > > The VC++ macro for the full source file path is $(InputPath), which > fails with NASM - but "$(InputPath)" works. That's because a macro is permitted to expand to several arguments - e.g. $(Opt) := ``-O2 -Oomg -Owtf -Obbq'' > The VC++ macro for the directory part of the path is $(InputDir) and > here both this and "$(InputDir)" fail when I attempt to use them with > the NASM -I switch. > > It is, of course, entirely possible that this is a VC++ bug. To get to the bottom of this, it's probably easiest to write a 3 line argv dumper, and see what the program actaully receives. Phil -- Ballmer: Developers developers developers developers Dubya: Terrorists terrorists terrorists terrorists |