Hi everyone,
This bundle is mostly for discussion. The idea is that "cabal install wxcore"
should really "just work". For Cabalised projects that use wxHaskell, the
difficulty of installing wxcore is a big stumbling block.
So what this patch bundle aims to do is to move us in the direction of o
This would be a first step in simplifying the auto-generation of the wxcore
stuff.
One thing I'm wondering though is do we really have to define these in
Eiffel? If we could rewrite them in C, it would make things feel a little
less exotic. Better yet, some of these constants appear to be define
Wed Apr 8 19:15:43 BST 2009 Eric Kow
* Remove seemingly unused external definitions in wxEiffel headers.
New patches:
[Remove seemingly unused external definitions in wxEiffel headers.
Eric Kow **20090408181543
Ignore-this: 40c03f17ee3c47e8c2aada12dcaaec3
] {
hunk ./wxc/eiffel/wx_defs.e 916
Here are three new patches which makes wxcore require wxc.
Does this move us closer to doing the right thing?
I'm still not sure what we need to do to account for bindist, though?
Previously sent
---
Wed Apr 8 11:38:47 BST 2009 Eric Kow
* Move wxcore.cabal to wxcore and use Simpl
On Fri, Jun 03, 2011 at 12:14:58 +0100, Jeremy O'Donoghue wrote:
>- Bugfix for assert error in SearchDynamicEventTable which was found in
>debug builds. I believe that this is a proper fix for an issue Eric noted a
>couple of months back.
It's not just debug builds (of what?), but basi
