Agent File Access

[Oliver Sampson]

Ah, sorry, I was a bit dense yesterday.  Hopefully, I'm not so dense
today.

Do I dare ask why a script would be the favored solution, and not
doing it directly in the code?  In CreateProcessA in
scheduler/process.c, each type of binary calls create_process.  Why
not just for the UNIX ones (BINARY_UNIX_EXE, BINARY_UNIX_LIB) swap out
all of the '\'s for '/'s in cmd_line?   

As far as setup and integration of Wine into the Unix environment, the
script solution seems much less transparent.

Oliver



On Tue, 07 Jan 2003 15:43:45 +0100, Rein Klazes <rklazes at xs4all.nl>
wrote:

>On Tue, 07 Jan 2003 14:44:53 +0000, you wrote:
>
>> Hi,
>> I'm not sue what winepath does, and the 'winepath --help' doesn't seem
>> to do much.
>
>I hoped the example would be enough. It does what I think you asked for,
>put path(s) known under wine and convert it to the unix path(s).
>
>> 
>> What I'm talking about for Agent in particular, is that when Agent as
>> a Windows program communicates with (for example) gimp as a unix
>> program and passes a command line parameter, like a file path (it
>> still thinks it's in C:\Data\agent rather than "~/data/agent", to
>> open, all of the back slashes should be changed to forward slashes.  
>> 
>> How would I use winepath in this situation?
>
>The command:
>
>  winepath 'C:\Data\agent'
>
>will output:
>
>  /home/yourself/data/agent
>
>Use that in a little script, call it perhaps winegimp, that calls gimp
>with the correct (unix) path. Something like:
>
>  #!/bin/sh
>  gimp `winepath "$@"`
>
>I use something similar to launch gvim on the patches on the mailing
>list. 
>
>Rein.

====================================================
Oliver Sampson                  
olsam at quickaudio.com
http://www.oliversampson.com