Issue with run.exe and PWD with spaces since last update (Cygwin 1.7.21)
Wed Jul 17 15:39:00 GMT 2013
On Jul 17 10:20, Charles Wilson wrote:
> On 7/17/2013 10:10 AM, Corinna Vinschen wrote:
> >Uhm. In that case, if ew *really* think your tools are the only
> >affected ones, Why do we bother to fix libcmain.c? Can't you then
> >simply provide your own main() in case of building for Cygwin?
> Perhaps, but I'm not sure of the ramifications. I think if you have
> a main() then you're going to get STD_HANDLES. Plus there's the
> whole concern about launching run.exe itself without a cmdbox,
> when it is used as a shortcut target.
In that case, the application gets the command line via GetCommandLine,
which in turn is converted to argc,argv by the Cygwin DLL ebfore calling
> This whole entrypoint thing is tied up in that, or at least it used
> to be. Now, that may ONLY apply to the mingw-compiled version,
> in which case I could do a
> #ifdef __CYGWIN__
> int main (int argc, char** argv)
> return realmain(argc, argv);
int main (int argc, char** argv)
int realmain (int argc, char** argv)
> and avoid the -e WinMain@16 link argument. (Except I think I arrange
> to only do -e WinMain@16 on mingw...hmm...)
Can you quickly check if that works? If so, we have a bit less pressure
to fix libcmain.
> If you look closely at WinMain, it basically parses the result from
> GetCommandLine() into argc,argv, and then delegates.
Yes, I saw that while debugging.
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Maintainer cygwin AT cygwin DOT com
Problem reports: http://cygwin.com/problems.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
More information about the Cygwin