X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=ghc%2Fdocs%2Fusers_guide%2Fwin32-dlls.sgml;h=0cb8b226eb5457bd2054222d4edd16a1dec85ee7;hb=2dfd507259664e6f28df4a9467a8de34d01d70a0;hp=cdaad9cd605ee179c6c8e57cc7315654e33ea246;hpb=dc801dc275fb8f81d482535b4d6317e234bb10f8;p=ghc-hetmet.git diff --git a/ghc/docs/users_guide/win32-dlls.sgml b/ghc/docs/users_guide/win32-dlls.sgml index cdaad9c..0cb8b22 100644 --- a/ghc/docs/users_guide/win32-dlls.sgml +++ b/ghc/docs/users_guide/win32-dlls.sgml @@ -112,7 +112,7 @@ make-sessions running under cygwin. Things to do - Don't use absolute paths in make, configure & co if there is any chance + Don't use absolute paths in make, configure & co if there is any chance that those might be passed to GHC (or to GHC-compiled programs). Relative paths are fine because cygwin tools are happy with them and GHC accepts '/' as path-separator. And relative paths don't depend on where cygwin's @@ -155,38 +155,37 @@ make-sessions running under cygwin. -Building and using Win32 DLLs - +Building and using Win32 DLLs + - -Dynamic link libraries, Win32 -DLLs, Win32 + +Dynamic link libraries, Win32 +DLLs, Win32 On Win32 platforms, the compiler is capable of both producing and using dynamic link libraries (DLLs) containing ghc-compiled code. This section shows you how to make use of this facility. - + - -Until recently, strip didn't work reliably on DLLs, so you + +Until recently, strip didn't work reliably on DLLs, so you should test your version with care, or make sure you have the latest binutils. Unfortunately, we don't know exactly which version of binutils cured the problem (it was supposedly fixed some years ago). - + - -Linking with DLLs - + +Linking with DLLs - + The default on Win32 platforms is to link applications in such a way that the executables will use the Prelude and system libraries DLLs, rather than contain (large chunks of) them. This is transparent at the command-line, so - + - - + + sh$ cat main.hs module Main where main = putStrLn "hello, world!" @@ -198,199 +197,198 @@ sh$ ls -l main.exe sh$ ./main hello, world! sh$ - - + + - -will give you a binary as before, but the main.exe + +will give you a binary as before, but the main.exe generated will use the Prelude and RTS DLLs instead of linking them in statically. - + - -4K for a "hello, world" application—not bad, huh? :-) - + +4K for a "hello, world" application—not bad, huh? :-) + - + - -Not linking with DLLs -<IndexTerm><Primary>-static option (Win32)</Primary></IndexTerm> + +Not linking with DLLs +<indexterm><primary>-static option (Win32)</primary></indexterm> - + If you want to build an executable that doesn't depend on any -ghc-compiled DLLs, use the option to link in +ghc-compiled DLLs, use the option to link in the code statically. - + - + Notice that you cannot mix code that has been compiled with - and not, so you have to use the + and not, so you have to use the option on all the Haskell modules that make up your application. - + - + - -Creating a DLL - + +Creating a DLL - + Making libraries into DLLs doesn't work on Windows at the moment (and is no longer supported); however, all the machinery is still there. If you're interested, contact the GHC team. Note that building an entire Haskell application as a DLL is still supported (it's just inter-DLL Haskell calls that don't work). -Creating a Win32 DLL -––mk-dll +Creating a Win32 DLL +––mk-dll Sealing up your Haskell library inside a DLL is straightforward; compile up the object files that make up the library, and then build the DLL by issuing a command of the form: - + - - + + ghc ––mk-dll -o foo.dll bar.o baz.o wibble.a -lfooble - - + + - -By feeding the ghc compiler driver the option , it + +By feeding the ghc compiler driver the option , it will build a DLL rather than produce an executable. The DLL will consist of all the object files and archives given on the command line. - + - + To create a `static' DLL, i.e. one that does not depend on the GHC DLLs, -use the when compiling up your Haskell code and +use the when compiling up your Haskell code and building the DLL. - + - + A couple of things to notice: - + - + - - - -Since DLLs correspond to packages (see ) you need -to use when compiling modules that + + + +Since DLLs correspond to packages (see ) you need +to use when compiling modules that belong to a DLL if you're going to call them from Haskell. Otherwise, Haskell code that calls entry points in that DLL will do so incorrectly, and crash. For similar reasons, you can only compile a single module tree into a DLL, -as startupHaskell needs to be able to call its -initialisation function, and only takes one such argument (see ). Hence the modules +as startupHaskell needs to be able to call its +initialisation function, and only takes one such argument (see ). Hence the modules you compile into a DLL must have a common root. - - + + - - + + By default, the entry points of all the object files will be exported from -the DLL when using . Should you want to constrain -this, you can specify the module definition file to use +the DLL when using . Should you want to constrain +this, you can specify the module definition file to use on the command line as follows: - + ghc ––mk-dll -o .... -optdll--def -optdllMyDef.def - + See Microsoft documentation for details, but a module definition file simply lists what entry points you want to export. Here's one that's suitable when building a Haskell COM server DLL: - + EXPORTS DllCanUnloadNow = DllCanUnloadNow@0 DllGetClassObject = DllGetClassObject@12 DllRegisterServer = DllRegisterServer@0 DllUnregisterServer = DllUnregisterServer@0 - - - + + + - - -In addition to creating a DLL, the option also + + +In addition to creating a DLL, the option also creates an import library. The import library name is derived from the name of the DLL, as follows: - + DLL: HScool.dll ==> import lib: libHScool_imp.a - + The naming scheme may look a bit weird, but it has the purpose of allowing the co-existence of import libraries with ordinary static libraries (e.g., -libHSfoo.a and -libHSfoo_imp.a. +libHSfoo.a and +libHSfoo_imp.a. Additionally, when the compiler driver is linking in non-static mode, it -will rewrite occurrence of on the command line to -. By doing this for you, switching from +will rewrite occurrence of on the command line to +. By doing this for you, switching from non-static to static linking is simply a question of adding - to your command line. + to your command line. - - - - + + + + - + - -Making DLLs to be called from other languages + +Making DLLs to be called from other languages - + If you want to package up Haskell code to be called from other languages, such as Visual Basic or C++, there are some extra things it is useful to -know. The dirty details are in the Foreign Function -Interface definition, but it can be tricky to work out how to +know. The dirty details are in the Foreign Function +Interface definition, but it can be tricky to work out how to combine this with DLL building, so here's an example: - + - + - - -Use foreign export declarations to export the Haskell + + +Use foreign export declarations to export the Haskell functions you want to call from the outside. For example, - + module Adder where adder :: Int -> Int -> IO Int -- gratuitous use of IO adder x y = return (x+y) foreign export stdcall adder :: Int -> Int -> IO Int - - - + + + - - + + Compile it up: - + ghc -c adder.hs -fglasgow-exts - + This will produce two files, adder.o and adder_stub.o - - + + - - -compile up a DllMain() that starts up the Haskell + + +compile up a DllMain() that starts up the Haskell RTS-––a possible implementation is: - + #include <windows.h> #include <Rts.h> @@ -413,59 +411,59 @@ DllMain } return TRUE; } - + -Here, Adder is the name of the root module in the module +Here, Adder is the name of the root module in the module tree (as mentioned above, there must be a single root module, and hence a single module tree in the DLL). Compile this up: - + ghc -c dllMain.c - - - + + + - - + + Construct the DLL: - + ghc ––mk-dll -o adder.dll adder.o adder_stub.o dllMain.o - + - - + + - - -Start using adder from VBA-––here's how I would -Declare it: + + +Start using adder from VBA-––here's how I would +Declare it: - + Private Declare Function adder Lib "adder.dll" Alias "adder@8" (ByVal x As Long, ByVal y As Long) As Long - + Since this Haskell DLL depends on a couple of the DLLs that come with GHC, make sure that they are in scope/visible. - + - + Building statically linked DLLs is the same as in the previous section: it -suffices to add to the commands used to compile up +suffices to add to the commands used to compile up the Haskell source and build the DLL. - + - + - + - + - +