On Fri, 2009-11-13 at 15:24 +, Jeremy O'Donoghue wrote:
> > So I take it that these modules are generated "from nothing" rather than
> > something like happy/alex pre-processors where the .hs files are
> > generated from .y/.x files. Cabal supports the latter fairly well and
> > you can add cu
On Thu, 12 Nov 2009 18:16 +, "Duncan Coutts"
wrote:
> On Thu, 2009-11-12 at 17:54 +, Jeremy O'Donoghue wrote:
> > Hi all,
> >
> > Another, probably simple, question regarding cabalization.
> >
> > Part of wxcore, the low level abstraction in wxHaskell, consists of
> > haskell modules w
I've had some luck with two techniques for this:
1. Create "stub" files, associated with a custom preprocessor which
knows how to parse them and generate a Haskell module. For example,
you might have "Foo.wx-stub" contain:
[headers]
wx/foo.h
wx/otherheader.h
and then parse it into pa
On Thu, 2009-11-12 at 17:54 +, Jeremy O'Donoghue wrote:
> Hi all,
>
> Another, probably simple, question regarding cabalization.
>
> Part of wxcore, the low level abstraction in wxHaskell, consists of
> haskell modules which are generated automatically by parsing C headers
> using another too
Hi all,
Another, probably simple, question regarding cabalization.
Part of wxcore, the low level abstraction in wxHaskell, consists of
haskell modules which are generated automatically by parsing C headers
using another tool, wxdirect.
When trying to create an sdist package, we run into the prob
