Changes between Version 7 and Version 8 of Building/CrossCompiling

Timestamp:

01/18/13 08:02:42 (5 months ago)

Author:

simonmar

Comment:

--

Building/CrossCompiling

@@ -72 +72 @@
 == Configuring the build ==
 
-To configure the build:
+The C cross-compiler and tools are usually installed with the platform name as a prefix, e.g. if the target platform is `arm-linux-gnueabihf` then the gcc cross-compiler is named `arm-linux-gnueabihf-gcc`.  If your cross-compiling toolset is set up like this, then add the directory containing the tools to your `PATH`, and just say:
+
+{{{
+./configure --target=<target>
+}}}
+
+and `configure` will find all the tools, using `<target>` as the prefix.
+
+If you need to specify the tools explicitly, then you can say
 
 {{{
@@ -78 +86 @@
 }}}
 
-Note: if you are cross-compiling for a platform that doesn't have a native code generator or registerised LLVM support, then you should add
+Note: if you are cross-compiling for a platform that doesn't have a native code generator or registerised LLVM support, then you should also add
 
 {{{
@@ -106 +114 @@
 You can do this even without installing your cross-compiler, just use `$TOP/inplace/bin/ghc-stage1` as `<cross-ghc>`.
 
-(the `--with-ld` option shouldn't really be required, hopefully this will get fixed at some point).
+NB. you should ensure that the cross-compiled packages won't conflict with your native packages; one way to do this is to modify your `$HOME/.cabal/config` to include the platform in the installation directory for packages:
+
+{{{
+install-dirs user
+  libsubdir: $arch-$os/$pkgid/$compiler
+}}}
+