On Tue, 2007-09-04 at 18:25 +0200, Sven Panne wrote:
On Tuesday 04 September 2007 03:16, Peter Gavin wrote:
[...] And if you consider that Cabal is trying to be autoconf, automake, and libtool, and make, in a single tool, there will be that many more kinks to work out :)
Huh? Cabal tries to be autoconf? Unless I've missed something, there's no way Cabal can help me to figure out the paths to OpenGL headers, the wildly varying linker options for OpenGL apps,
Well, if the library you're binding to happens to be one of the 350+ that use pkg-config then cabal can indeed find the paths to the headers and the varying linker options (by asking pkg-config). pkgconfig-depends: gtk+-2.0 >= 2.8, cairo This is a new feature in Cabal-1.2. Of course it doesn't help for libs like GL that don't provide pkg-config files.
if the installed OpenAL's alcCloseDevice returns void or an int,
That's trickier.
the matching Haskell type for an ALuint, etc.
c2hs can do that. Sure, it's not an autoconf replacement and though you can use Setup.lhs to do some of those things, the api is not sufficiently stable to recommend using that yet. Duncan