- Cvs-hugs - Haskell.org

cvs commit: hugs98/src/msc ffihugs.bat
by Neil Mitchell 26 Apr '06

26 Apr '06

neil 2006/04/26 14:40:58 PDT Modified files: src/msc ffihugs.bat Log: Update the batch file to work with certain quoting mechanisms employed by Cabal Revision Changes Path 1.2 +2 -2 hugs98/src/msc/ffihugs.bat

1 0

cvs commit: hugs98/docs/users_guide faq.xml
by Ross Paterson 26 Apr '06

26 Apr '06

ross 2006/04/26 13:43:05 PDT Modified files: docs/users_guide faq.xml Log: point at bug tracking system Revision Changes Path 1.6 +6 -3 hugs98/docs/users_guide/faq.xml

1 0

cvs commit: hugs98 RPM.mk
by Ross Paterson 26 Apr '06

26 Apr '06

ross 2006/04/26 13:34:10 PDT Modified files: . RPM.mk Log: remove _darcs properly Revision Changes Path 1.49 +2 -2 hugs98/RPM.mk

1 0

cvs commit: hugs98/src machdep.c
by Neil Mitchell 26 Apr '06

26 Apr '06

neil 2006/04/26 11:54:36 PDT Modified files: src machdep.c Log: Reorder the options for ffihugs See http://www.haskell.org//pipermail/cvs-hugs/2006-April/003433.html Revision Changes Path 1.138 +7 -7 hugs98/src/machdep.c

1 0

Windows FFI patch
by Neil Mitchell 26 Apr '06

26 Apr '06

Hi, Attached is a patch that is useful (but not essential) for Windows FFI to work slightly better. Hugs builds up a command line that it passes to the compiler, for example: gcc -blah1 <filename> -blah2 In certain compilers -blah2 would not apply to <filename>, as a result when compiling with MSVC, the use of blah2 after <filename> generates a warning, but still works. The simple solution is the attached patch which moves -blah2 before <filename>. Does this harm gcc? If not then its probably a useful patch. If yes, then I'll get over it. There are a few other patches required for FFI - since the command line used by Hugs in the tree hasn't worked with visual studio compilers for a long time - I'll commit some patches tonight. With these tweaks, ffihugs works just great with windows. The only thing potentially missing is a warning that your carefully written C file is about to be trashed by ffihugs if you do the "obvious" thing. Or perhaps hugs should use a different name for the file generates, like test.temp.hugs.c ? Just anything thats less likely to clash. Thanks Neil

2 3

cvs commit: hugs98/src/msc config.h ffihugs.bat
by Neil Mitchell 26 Apr '06

26 Apr '06

neil 2006/04/26 11:10:32 PDT Modified files: src/msc config.h Added files: src/msc ffihugs.bat Log: Added support for ffihugs with visual studio 2003 Revision Changes Path 1.30 +1 -1 hugs98/src/msc/config.h

1 0

cvs commit: hugs98/docs/users_guide others.xml
by Ross Paterson 26 Apr '06

26 Apr '06

ross 2006/04/26 09:53:29 PDT Modified files: docs/users_guide others.xml Log: fix the ffihugs example for Windows (presumably the -lm is wrong too?) Revision Changes Path 1.3 +19 -10 hugs98/docs/users_guide/others.xml

1 0

Using hugsffi
by Neil Mitchell 26 Apr '06

26 Apr '06

Hi, I now can build ffihugs, and have added some patches so it finds visual studio etc. I'm currently have ffihugs do something "unexpected" - but I'm not sure what the real behaviour is... -- test.hs import Foreign import System.Environment main = print $ c_test 1 2 foreign import ccall unsafe "test.h test" c_test :: Int -> Int -> Int -- test.c int test(int a, int b){return 42;} -- test.h int test(int a, int b); Then I run (as per http://cvs.haskell.org/Hugs/pages/users_guide/ffihugs.html) ffihugs test.hs test.c And before compiling hugs has clobbered test.c, and removed my code from it. This gives a link error, since test is undefined. Is this how ffihugs is supposed to work? Should my code be going somewhere else? Thanks Neil

2 1

cvs commit: hugs98/src/msc hugs.sln ffihugs.vcproj
by Neil Mitchell 26 Apr '06

26 Apr '06

neil 2006/04/26 07:15:47 PDT Modified files: src/msc hugs.sln Added files: src/msc ffihugs.vcproj Log: Add an ffihugs project for visual studio Revision Changes Path 1.2 +8 -0 hugs98/src/msc/hugs.sln

1 0

Compiling ffihugs
by Neil Mitchell 26 Apr '06

26 Apr '06

Hi, Where is the main procedure for ffihugs? I'm not sure really where it is, or how to go about building it. Just a general pointer to the main, and I should be able to chase the dependancies from there. Thanks Neil

2 1