On 02.12.2007, at 22:34, Eric Sessoms wrote:
Just add
Build-Tools: c2hs
And cabal will take it from there.
thanks eric, that's really pleasingly simple (it appears that the
Build-Tools: line isn't even needed).
sk
___
Haskell-Cafe mailing list
On Tue, 2007-12-11 at 19:14 +0100, Stefan Kersten wrote:
On 02.12.2007, at 22:34, Eric Sessoms wrote:
Just add
Build-Tools: c2hs
And cabal will take it from there.
thanks eric, that's really pleasingly simple
(it appears that the Build-Tools: line isn't even needed).
Though note
hi,
i'm looking for a way to integrate c2hs (single .chs file) in a cabal
build setup; can anybody give me some hints?
thanks,
sk
___
Haskell-Cafe mailing list
Haskell-Cafe@haskell.org
http://www.haskell.org/mailman/listinfo/haskell-cafe
Just add
Build-Tools: c2hs
And cabal will take it from there.
Stefan Kersten wrote:
hi,
i'm looking for a way to integrate c2hs (single .chs file) in a cabal
build setup; can anybody give me some hints?
thanks,
sk
___
Haskell-Cafe mailing list
On Wed, Nov 29, 2006 at 03:38:24 +, Duncan Coutts wrote:
On Tue, 2006-11-28 at 17:24 +, Magnus Therning wrote:
On Tue, Nov 28, 2006 at 12:00:50 +, Magnus Therning wrote:
[..]
Can't really see anything obviously bogus about the following:
% cat Foo.chs
module Foo where
On Wed, 2006-11-29 at 11:26 +, Magnus Therning wrote:
Or the simpler way is to include in your .cabal file:
extensions: ForeignFunctionInterface
That then applies to every module in the lib and has the advantage of
being portable between compilers.
Ah, good point.
Now, where
On Wed, Nov 29, 2006 at 01:12:50PM +, Duncan Coutts wrote:
http://www.haskell.org/cabal/release/latest/doc/users-guide/x30.html#buildinfo
Section 2.1.4, though I do notice that the link to the full list of
extensions is broken.
This version works (and looks better too):
On Tue, Nov 28, 2006 at 00:33:42 +, Duncan Coutts wrote:
On Mon, 2006-11-27 at 22:26 +, Magnus Therning wrote:
Can I use cabal to build packages that incorporates C libraries and FFI
Haskell created using c2hs?
Yes you can. Cabal understands a bit about .chs files. I think all you
need
On Tue, Nov 28, 2006 at 11:11:30 +, Duncan Coutts wrote:
On Tue, 2006-11-28 at 10:56 +, Magnus Therning wrote:
On Tue, Nov 28, 2006 at 00:33:42 +, Duncan Coutts wrote:
On Mon, 2006-11-27 at 22:26 +, Magnus Therning wrote:
Can I use cabal to build packages that incorporates C
On Tue, Nov 28, 2006 at 12:00:50 +, Magnus Therning wrote:
[..]
Can't really see anything obviously bogus about the following:
% cat Foo.chs
module Foo where
#include foo.h
fooOne i = {# call foo1 #} i
I solved my problem, but thought I'd send a mail to the list for anyone
who's
On Tue, 2006-11-28 at 17:24 +, Magnus Therning wrote:
On Tue, Nov 28, 2006 at 12:00:50 +, Magnus Therning wrote:
[..]
Can't really see anything obviously bogus about the following:
% cat Foo.chs
module Foo where
#include foo.h
fooOne i = {# call foo1 #} i
I solved
Can I use cabal to build packages that incorporates C libraries and FFI
Haskell created using c2hs?
Any pointers on how to do that?
/M
--
Magnus Therning (OpenPGP: 0xAB4DFBA4)
[EMAIL PROTECTED] Jabber: [EMAIL PROTECTED]
http://therning.org/magnus
On Mon, 2006-11-27 at 22:26 +, Magnus Therning wrote:
Can I use cabal to build packages that incorporates C libraries and FFI
Haskell created using c2hs?
Yes you can. Cabal understands a bit about .chs files. I think all you
need to do is specify the module in the exposed-modules or
13 matches
Mail list logo
