On Mon, Jan 5, 2009 at 2:14 PM, Lars Nilsson <[email protected]> wrote: > On Mon, Jan 5, 2009 at 3:14 AM, felix winkelmann <[email protected]> wrote: >> The handling of backslashes as escaping characters is not the problem, >> it seems. If I pass this string (verbatim, just like it is printed here) to >> system(3): >> >> "c:\home\chicken-trunk\bin\csi" -bnq -e "(require-library setup-api)" >> -e "(import setup-api)" "c:\...some...path...\defstruct.setup" >> >> I get an error message that tells me that the program >> >> "c:\home\chicken-trunk\bin\csi" -bnq -e "" >> >> (sic) can not be found. > > Perhaps you could try the short-name paths in Windows, like > c:\home\chicke~1\bin\csi, without the quotes around it. > > If that works, perhaps use GetShortPathName() to automatically find > out what the "short" path is for a "full" path.
Hey, this might be part of a solution. But what about spaces in pathnames (where the filename part is <7 characters)? cheers, felix _______________________________________________ Chicken-users mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/chicken-users
