I was wondering whether there was any standard way to find HsFFI.h? I
can hardcode it into my makefiles for my own projects, but when i
distribute code, I end up having to add -I lines for every possible
location of it, usually multiplied by every compiler version
it supports
since that is
On Wed, Oct 30, 2002 at 09:12:01AM -, Simon Marlow wrote:
If this isn't possible, then you can extract the information from the
output of 'ghc -v'. The relevant directory is in the include_dirs field
of the rts package.
michaelw@stargate:~$ ghc
John:
I was wondering whether there was any standard way to find HsFFI.h?
Simon:
If you're using GHC, the trick is to use GHC to compile your C code
too because it adds the appropriate -I flag to the gcc command line.
And if using Hugs (forthcoming release), use ffihugs to compile your C
On Wed, Oct 30, 2002 at 09:12:01AM -, Simon Marlow wrote:
If this isn't possible, then you can extract the
information from the
output of 'ghc -v'. The relevant directory is in the
include_dirs field
of the rts package.
michaelw@stargate:~$ ghc
I was wondering whether there was any standard way to find HsFFI.h? I
can hardcode it into my makefiles for my own projects, but when i
distribute code, I end up having to add -I lines for every possible
location of it, usually multiplied by every compiler version it supports
since that is often
