Re: [Audacity-devel] Another Cygwin Patch (command line parser)

[Dominic M. <do...@mi...>]

Dave Fancella wrote:
> Dave Fancella wrote:
> 
>> I forgot to mention that the patch is against 1.2.  Um, should I be 
>> patching to 1.2 or head, right now?  I know that cygwin support isn't 
>> needed for 1.2, and I'm looking into wxCmdLineParser as a possible way 
>> of solving this other problem.  There's potential to break the 
>> commandline there, so I was thinking it should probably go against 
>> head instead.  Thoughts? 
> 
> This patch is also against 1.2, and it adds a command line parser for 
> cygwin (wxCmdLineParser didn't work, had unresolved symbols, so I copped 
> out).  I decided for clarity at this time it would be simpler to just 
> copy the existing one and catch it in an ifdef, so it shouldn't affect 
> any other platforms in any way.  :)

OK, I applied both of these patches.  When your computer is working
again, it'd be great if you could confirm that Cygwin now compiles
'out of the box', assuming you pass the right options to configure.

> The bug turned out to be really weird.  Let's say you have the 
> executable stored at this path:
> C:\Program Files\AudacityPro
> 
> In AudacityApp, we'd get, as argv[0], this:
> C:\Program Files\AudacityPro\audacity.exe
> 
> As argv[1] we'd get:
> Files\AudacityPro\audacity.exe
> 
> And Audacity would throw up a dialog saying "Can't open 
> Files\AudacityPro\audacity.exe".  Weird.

I think I was having similar problems on Mac OS X.  We should probably
suggest a fix for wx 2.5.

- Dominic


> Dave