On 7/17/2013 11:52 AM, Charles Wilson wrote:
On 7/17/2013 10:54 AM, Charles Wilson wrote:
On 7/17/2013 10:33 AM, Corinna Vinschen wrote:
Can you quickly check if that works? If so, we have a bit less pressure
to fix libcmain.
Seems to work for run2.exe. Stay tuned for checkX.exe and run.exe.
I've uploaded run2-0.4.2-2 as a test release for both 32bit and 64bit.
However, run is more complicated; most of the application code is
actually in WinMain. I've been meaning to refactor it more along the
lines of run2, but never got around to it. Looks like I now have a
reason...but it'll take a bit longer to do, and I won't really have time
to address it until Saturday.
run-1.3.0 should operate normally, on cygwin-1.7.21 or cygwin-1.7.22
(well, really, any version of cygwin-1.7.x) Note that this distribution
of run-1.3.0 (a) was compiled on cygwin-1.7.21, so it does not take
advantage of the compile-time fix provided by cygwin-1.7.22 [1], and (b)
on __CYGWIN__ it uses the main() entry point rather than WinMain@16, and
so does not access GetCommandLine() anyway (although it does use
GetCommandLine(), when built for mingw[64,.org] targets)
[1] http://cygwin.com/ml/cygwin/2013-07/msg00438.html
- Added cygwin GetCommandLine wrappers which will allow Cygwin programs to
(appear to) use the Windows command line functions.
--
Chuck
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
