X-Git-Url: http://git.megacz.com/?p=ghc-hetmet.git;a=blobdiff_plain;f=docs%2Fusers_guide%2Fwin32-dlls.xml;h=703bb1877dd636a7ef49e8d03a351b06e314068f;hp=1589821b0e815d205a93cde1a1e0a984eaa8218f;hb=dcf739bd7fb7de140be3bafb4ce211e2e5c7bba9;hpb=e929beed06e43151e2f91b34962c405e05fabb3a diff --git a/docs/users_guide/win32-dlls.xml b/docs/users_guide/win32-dlls.xml index 1589821..703bb18 100644 --- a/docs/users_guide/win32-dlls.xml +++ b/docs/users_guide/win32-dlls.xml @@ -294,7 +294,7 @@ option on all the Haskell modules that make up your application. Creating a Win32 DLL -––shared +–shared 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: @@ -302,12 +302,12 @@ the DLL by issuing a command of the form: -ghc ––shared -o foo.dll bar.o baz.o wibble.a -lfooble +ghc –shared -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. @@ -347,12 +347,12 @@ 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 +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 ––shared -o .... MyDef.def +ghc –shared -o .... MyDef.def See Microsoft documentation for details, but a module definition file @@ -371,7 +371,7 @@ EXPORTS -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: @@ -485,7 +485,7 @@ ghc -c dllMain.c Construct the DLL: -ghc ––shared -o adder.dll adder.o adder_stub.o dllMain.o +ghc –shared -o adder.dll adder.o adder_stub.o dllMain.o