X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Fphases.xml;h=7f3f139cce95616ab724f7459506215f1b2d2ffb;hb=5263c9ab4408e3b62dbf7505ab40a81946d4e49b;hp=cd18469e81638301e28f1a5ea0575a04fa070173;hpb=ba5729e5b8d80b3fcc8a477cb36d6a03800ac0dd;p=ghc-hetmet.git diff --git a/docs/users_guide/phases.xml b/docs/users_guide/phases.xml index cd18469..7f3f139 100644 --- a/docs/users_guide/phases.xml +++ b/docs/users_guide/phases.xml @@ -113,7 +113,19 @@ - + + + cmd + + + + Use cmd as the + program to use for embedding manifests on Windows. Normally this + is the program windres, which is supplied with a + GHC installation. See in . + + @@ -121,7 +133,7 @@ Forcing options to a particular phase forcing GHC-phase options - Options can be forced through to a particlar compilation + Options can be forced through to a particular compilation phase, using the following flags: @@ -210,6 +222,18 @@ dependency generator. + + + option + + + + Pass option to + windres when embedding manifests on Windows. + See in . + + So, for example, to force an @@ -388,7 +412,7 @@ $ cat foo.hspp This symbol is defined when pre-processing Haskell (input) and pre-processing C (GHC output). Since GHC from - verion 4.00 now supports concurrent haskell by default, + version 4.00 now supports concurrent haskell by default, this symbol is always defined. @@ -567,9 +591,7 @@ $ cat foo.hspp Use GHC's native code generator rather than compiling via C. This will compile faster (up to twice as fast), but may produce code that is slightly slower than - compiling via C. is the default - when optimisation is off (see ). + compiling via C. is the default. @@ -580,9 +602,8 @@ $ cat foo.hspp Compile via C instead of using the native code - generator. This is default for optimised compilations, - and on architectures for which GHC doesn't have a native - code generator. + generator. This is the default on architectures for which GHC + doesn't have a native code generator. @@ -600,6 +621,32 @@ $ cat foo.hspp + + + + + Generate object code. This is the default outside of + GHCi, and can be used with GHCi to cause object code to be + generated in preference to bytecode. + + + + + + + + + + Generate byte-code instead of object-code. This is + the default in GHCi. Byte-code can currently only be used + in the interactive interpreter, not saved to disk. This + option is only useful for reversing the effect of + . + + + + + @@ -621,10 +668,7 @@ $ cat foo.hspp When generating code, assume that entities imported from a different package will reside in a different shared library or - binary. This currently works on Mac OS X; it works on PowerPC Linux when - using the native code generator. As with , - x86 Linux support is not quite ready yet. Windows is not supported, - and it is a no-op on PowerPC64 Linux. + binary. Note that this option also causes GHC to use shared libraries when linking. @@ -791,10 +835,10 @@ $ cat foo.hspp - Tell the linker to use shared Haskell libraries, if - available (this option is only supported on Mac OS X at the - moment, and also note that your distribution of GHC may - not have been supplied with shared libraries). + This flag switches to shared Haskell libraries for + linking. See on how to + create them. + Note that this option also has an effect on code generation (see above). @@ -802,6 +846,36 @@ $ cat foo.hspp + + + + + Instead of creating an executable, GHC produces a + shared object with this linker flag. Depending on the + operating system target, this might be an ELF DSO, a Windows + DLL, or a Mac OS dylib. GHC hides the operating system + details beneath this uniform flag. + + The flags / control whether the + resulting shared object links statically or dynamically to + Haskell package libraries given as option. Non-Haskell + libraries are linked as gcc would regularly link it on your + system, e.g. on most ELF system the linker uses the dynamic + libraries when found. + + Object files linked into shared objects must be + compiled with , see + + When creating shared objects for Haskell packages, the + shared object must be named properly, so that GHC recognizes + the shared object when linked against this package. See + shared object name mangling. + + + + + + specifying your own main function @@ -899,7 +973,7 @@ $ cat foo.hspp Parallelismparallelism on a multiprocessormultiprocessorSMP or multicoremulticore - machine. See . + machine. See . The ability to make a foreign call that does not block all other Haskell threads. @@ -921,6 +995,72 @@ $ cat foo.hspp url="../libraries/base/Control.Concurrent.html">Control.Concurrent module. + + + + + + + + + On Windows, GHC normally generates a + manifestmanifest + file when linking a binary. The + manifest is placed in the file + prog.exe.manifest + where prog.exe is the name of the + executable. The manifest file currently serves just one purpose: + it disables the "installer detection"installer detection + in Windows Vista that + attempts to elevate privileges for executables with certain names + (e.g. names containing "install", "setup" or "patch"). Without the + manifest file to turn off installer detection, attempting to run an + executable that Windows deems to be an installer will return a + permission error code to the invoker. Depending on the invoker, + the result might be a dialog box asking the user for elevated + permissions, or it might simply be a permission denied + error. + + Installer detection can be also turned off globally for the + system using the security control panel, but GHC by default + generates binaries that don't depend on the user having disabled + installer detection. + + The disables generation of + the manifest file. One reason to do this would be if you had + a manifest file of your own, for example. + + In the future, GHC might use the manifest file for more things, + such as supplying the location of dependent DLLs. + + also implies + , see below. + + + + + + + + + + + The manifest file that GHC generates when linking a binary on + Windows is also embedded in the executable itself, by default. + This means that the binary can be distributed without having to + supply the manifest file too. The embedding is done by running + windreswindres + ; to see exactly what GHC does to embed the manifest, + use the flag. A GHC installation comes with + its own copy of windres for this reason. + + See also () and + (). + +