On Sunday, 15.11.09 at 18:05, Conal Elliott wrote:
> I will be thrilled to switch from gtk2hs back to wxHaskell for all of
> my GUI-ful projects as soon as the ghci-killing problem (crash on
> second 'start') is solved. Any progress?
Thanks for reminding.
I ran the death program like this:
$ cat
On Saturday, 26.09.09 at 06:59, Eric Y. Kow wrote:
> > cabal install
> > --extra-include-dirs=/c/brian/tools/ghc-6.10.4/include/mingw/c++/3.4.5
> > --extra-include-dirs=/c/brian/tools/ghc-6.10.4/include/mingw/c++/3.4.5/mingw32/
> > --extra-include-dirs=/c/SourceCode/Libraries/wxWidgets2.8/contrib/i
I didn't get it to work, but maybe I made some progress.
I installed wxWidgets by installing wxPack, a binary distribution. I did
it that way just because I didn't know what else to do.
Like Lyle Kopnicky mentioned, wx-config(1) doesn't come with wxWidgets.
I attribute it to the fundamental theor
I'll check out the situation in Windows tonight.
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do be
On Tuesday, 11.08.09 at 20:03, Brian Lewis wrote:
> You might try adding
> ["-DwxcREFUSE_OPENGL", "-DwxcREFUSE_MEDIACTRL"]
> to your cppOptions.
Sorry, I meant 'ccOptions'. After I did that, I was able to do 'ghc
--make Bo
On Tuesday, 11.08.09 at 23:27, Eric Y. Kow wrote:
> Now I'm getting errors like the below. I think in the old configure
> script and makefile we had to pass in special flags for glcanvas,
> but I could be wrong.
You might try adding
["-DwxcREFUSE_OPENGL", "-DwxcREFUSE_MEDIACTRL"]
to your cppOptio
On Tuesday, 11.08.09 at 23:27, Eric Y. Kow wrote:
> I've also pushed some stuff removing wxc modules which I think wxHaskell
> does not support (I based this on ls dist/wxc/*.o)
OK, thank you. I'll check that out.
I just pushed stuff that causes wxcore to actually install for me in
Linux. No idea
On Tuesday, 11.08.09 at 15:13, Brian Lewis wrote:
> On Tuesday, 11.08.09 at 15:08, Brian Lewis wrote:
> > src/cpp/eljfl.cpp:1277:0:
> > error: conversion from ‘char*’ to ‘const wxString’ is ambiguous
>
> http://wiki.wxwidgets.org/WxString
I pushed some stuff to the gith
On Tuesday, 11.08.09 at 15:08, Brian Lewis wrote:
> src/cpp/eljfl.cpp:1277:0:
> error: conversion from ‘char*’ to ‘const wxString’ is ambiguous
http://wiki.wxwidgets.org/WxString
--
Let Crystal Reports hand
On Tuesday, 11.08.09 at 02:05, Eric Y. Kow wrote:
> setup: Missing dependency on a foreign library:
> * Missing C library: wx_macud-2.8
>
> I guess the Setup.hs file needs to call wx-config
Hmm. But it does. Does 'wx-config --cppflags --libs' show the stuff it
should? Where is the build failing fo
I made a repo with wxcore and wxc together and tried to make a
wxcore.cabal that would replace the existing makefile:
http://github.com/bsl/wxcore/tree/master
It doesn't build completely for me, but maybe it's a start.
--
I think it'd be good to replace the darcs wxhaskell/makefile with
wxhaskell.cabal, if possible.
One of the first things the makefile does is build wxdirect, so I split
it off and cleaned it up a little bit:
http://github.com/bsl/wxdirect/tree/master . It could be put on HDB. My
intention is that l
On Sunday, 09.08.09 at 00:15, Eric Y. Kow wrote:
> Does this work better?
> cabal install wx --configure-opt="--user --enable-split-objs --hcprof"
I'll try. Thanks.
> In the darcs version of wxHaskell, I've also attempted to split
> wxcore off so that it is cleanly Cabalised (just the Simple buil
On Saturday, 08.08.09 at 23:24, S. Doaitse Swierstra wrote:
> http://noordering.wordpress.com/2009/04/21/cabals-default-install-location/
I don't think that's relevant, firstly, because my ~/.cabal/config says
explicitly to install packages in ~/.cabal, and secondly, because the wx
cabal package s
nder ~/.cabal.
> On 8 aug 2009, at 03:09, Brian Lewis wrote:
>> I appreciate all the hard work that went into WxHaskell, and the
>> effort
>> going into its continued development. But:
>>
>> $ cabal install wx
>> ...
>> Writing new package config fi
On Saturday, 08.08.09 at 20:37, S. Doaitse Swierstra wrote:
> But this suggests that your Haskell installation is a global one, so
> you should us:
>
> sudo cabal install wx
I absolutely should *not* do that. It's not reasonable for the wx cabal
package to modify files under the jurisdiction of so
I appreciate all the hard work that went into WxHaskell, and the effort
going into its continued development. But:
$ cabal install wx
...
Writing new package config file...
ghc-pkg: /usr/lib/ghc-6.10.4/./package.conf:
you don't have permission to modify this file
Is there some explanation for thi
17 matches
Mail list logo