[Cook] dos-path / un-dos-path is anachronistic
John Darrington
john at cellform.com.au
Tue Aug 24 13:42:27 EST 2004
On Mon, Aug 23, 2004 at 10:09:02PM -0400, Chuck_Eaker at mapinfo.com wrote:
Some of us need to pass dosified paths to Win32 and .NET tools such as the
compilers and Visual Studios. It turns out, though, at least in my case,
that they have to go through the Linux shell on the machine that cook is
running on, then through the shell of the remote Win32 machine. This means
that every backslash in a dos path has to be replaced with four backslashes
by cook before the command in which it appears is executed.
Isn't that what the [quote ...] command is for?
So, don't mess with it.
It won't affect paths on the W32 format. Only paths converted from
w32 into cygwin. As per my example: C:\Temp becomes //C/Temp whereas
it ought to become /cygdrive/C/Temp
J'
--
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://wwwkeys.pgp.net or any PGP keyserver for public key.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://lists.auug.org.au/pipermail/cook-users/attachments/20040824/a09caf78/attachment.pgp>
More information about the Cook-users
mailing list