I finally solved the compile problem. Running "cabal clean” in the original
tree fixed it. I have no idea how it mucked with the sandbox, but it did. After
I did the clean, even more things failed, but after recreating the sandbox it
worked. I had tried to recreate the sandbox before and it did
Henk-Jan,
I think you are right about Windows, but it does pass them on Linux, and this
does make my app work on Ubuntu. It is not the RTS args that are the problem,
it is the args for the application that come after. Windows has the further
problem of bypassing the passed args completely. My t
On Sat, 04 Apr 2015 21:19:43 +0200, Michael Jones
wrote:
> I have made a solution to the args problem. To review, if the latest
> code on github is used on Ubuntu, and if agreements are passed on the
> command line of the application, wxHaskell does a “getArgs” and passes
> them on, and t
I have made a solution to the args problem. To review, if the latest code on
github is used on Ubuntu, and if agreements are passed on the command line of
the application, wxHaskell does a “getArgs” and passes them on, and then there
is an error on the command line. On Windows with the most rece
I also notice that if I use the git repo:head for wxHaskell on Linux, I get a
similar error + Usage as windows, but on the command line. The version of
wxHaskell that cabal fetches does not have this problem.
On windows, I took the repo:head because the released wxHaskell that cabal
downloads
There is a response from wxWidgets trac
#16935:
http://trac.wxwidgets.org/ticket/16935#comment:1
On Mar 28, 2015, at 5:12 PM, Henk-Jan van Tuyl wrote:
> On Wed, 25 Mar 2015 22:57:12 +0100, Michael Jones
> wrote:
>
>> On Win 7...
>>
>> The latest code on github seems to result in a wxWidgets
On Wed, 25 Mar 2015 22:57:12 +0100, Michael Jones
wrote:
> On Win 7...
>
> The latest code on github seems to result in a wxWidgets call to LPTSTR
> WINAPI GetCommandLine(void);
>
> This results in popping a dialog complaining about command options. On
> Linux this does not happen. Looks like
On Win 7...
The latest code on github seems to result in a wxWidgets call to LPTSTR WINAPI
GetCommandLine(void);
This results in popping a dialog complaining about command options. On Linux
this does not happen. Looks like wxWidgets is trying to use this call to deal
with unicode, but it unfor
