Mail Archives: cygwin-apps/2000/07/16/00:21:51
Sorry, I should explain more
exec("C:/cygwin/usr/local/program.exe") fails
exec("C:\\cygwin\usr\local\program.exe") works (\\ c-style escaped)
and program.exe receives the first format from start|run, and from
shortcuts, or double-clicking on a program. So having a program that calls
exec based in it's own path will need an library call equivalent to
cygpath -u (which looks to be cygwin_conv_to_posix_path(name,
convertedname), or for argv[0] to be a little more consistent.
I've put cygwin_conv_to_posix_path in the program I'm working on, All i'm
saying is that a longer term solution might be to put something in the
startup code..
Rob
----- Original Message -----
From: "Chris Faylor" <cgf AT cygnus DOT com>
To: "cygapp" <cygwin-apps AT sourceware DOT cygnus DOT com>
Sent: Sunday, July 16, 2000 1:45 PM
Subject: Re: two questions
> On Sun, Jul 16, 2000 at 01:45:56PM +1000, Robert Collins wrote:
> >1)Start|run, c:\cygwin\usr\local\program.exe
> >2)start|run, cmd (running win2k). then (from any drive)
> >"c:\cygwin\usr\local\program.exe"
> >
> >in 1, argv[0] is C:/cygwin/usr/local/program.exe
> >in 2, argv[0] is /usr/local/program.exe
> >
> >Note that bash was not the shell in 2! I'm quite happy to code around
this
> >myself, but if someone wanted to provide a pointer as to where I should
> >place it I'm happy to code around it for cygwin..
> >
> >The reason it's a issue, is that I want to call
exec(argv[0],newswitches),
> >which the above behaviour scuttles..
>
> Why?
>
> cgf
>
- Raw text -