X-Git-Url: http://git.megacz.com/?a=blobdiff_plain;f=docs%2Fusers_guide%2Futils.xml;fp=docs%2Fusers_guide%2Futils.xml;h=109cc017527105395cdefbcd534f633bcf71dd6f;hb=4a2a508bb6adf33f9f3e99baa85f73f0fc18c832;hp=0c7f0f6131f34eb14248cf3279ab17d2e2102186;hpb=90d7a88f304ddff15f31f9b1edb86b452679583b;p=ghc-hetmet.git
diff --git a/docs/users_guide/utils.xml b/docs/users_guide/utils.xml
index 0c7f0f6..109cc01 100644
--- a/docs/users_guide/utils.xml
+++ b/docs/users_guide/utils.xml
@@ -270,6 +270,34 @@ tags:
+ -k or
+ ––keep-files
+
+ Proceed as normal, but do not delete any intermediate files.
+
+
+
+
+ -x or
+ ––cross-compile
+
+ Activate cross-compilation mode (see ).
+
+
+
+
+ ––cross-safe
+
+ Restrict the .hsc directives to those supported by the
+ --cross-compile mode (see ).
+ This should be useful if your .hsc files
+ must be safely cross-compiled and you wish to keep
+ non-cross-compilable constructs from creeping into them.
+
+
+
+
+
-? or ––help
Display a summary of the available flags and exit successfully.
@@ -544,6 +572,29 @@ tags:
+
+ Cross-compilation
+
+ hsc2hs normally operates by creating, compiling,
+ and running a C program. That approach doesn't work when cross-compiling --
+ in this case, the C compiler's generates code for the target machine,
+ not the host machine. For this situation, there's
+ a special mode hsc2hs --cross-compile which can generate
+ the .hs by extracting information from compilations only -- specifically,
+ whether or not compilation fails.
+
+
+ Only a subset of .hsc syntax is supported by
+ --cross-compile. The following are unsupported:
+
+ #{const_str}
+ #{let}
+ #{def}
+ Custom constructs
+
+
+
+