[FE training-materials-updates] setting ARCH and CROSS_COMPILE: more neutral advise

Michael Opdenacker michael.opdenacker at free-electrons.com
Thu Oct 4 14:42:30 CEST 2012


Repository : git://git.free-electrons.com/training-materials.git

On branch  : master
Link       : http://git.free-electrons.com/training-materials/commit/?id=546b3c74461e06caefd2489e35f3de4e684c0707

>---------------------------------------------------------------

commit 546b3c74461e06caefd2489e35f3de4e684c0707
Author: Michael Opdenacker <michael.opdenacker at free-electrons.com>
Date:   Thu Oct 4 14:41:33 2012 +0200

    setting ARCH and CROSS_COMPILE: more neutral advise
    
    Leave it up to the trainer to recommend one solution or the other


>---------------------------------------------------------------

546b3c74461e06caefd2489e35f3de4e684c0707
 .../sysdev-linux-intro-cross-compilation.tex       |   15 +++++++++------
 1 file changed, 9 insertions(+), 6 deletions(-)

diff --git a/slides/sysdev-linux-intro-cross-compilation/sysdev-linux-intro-cross-compilation.tex b/slides/sysdev-linux-intro-cross-compilation/sysdev-linux-intro-cross-compilation.tex
index a643a2b..f4b4322 100644
--- a/slides/sysdev-linux-intro-cross-compilation/sysdev-linux-intro-cross-compilation.tex
+++ b/slides/sysdev-linux-intro-cross-compilation/sysdev-linux-intro-cross-compilation.tex
@@ -49,17 +49,20 @@
   \item Pass \code{ARCH} and \code{CROSS_COMPILE} on the \code{make}
     command line: \\
     \code{make ARCH=arm CROSS_COMPILE=arm-linux- ...} \\
-    Not recommended, because you can screw up your build and
-    configuration if you ever forget to pass these variables when
-    you run any \code{make} command.
+    Drawback: it is easy to forget to pass these variables when
+    you run any \code{make} command, causing your build and
+    configuration to be screwed up.
   \item Define \code{ARCH} and \code{CROSS_COMPILE} as environment
     variables: \\
     \code{export ARCH=arm} \\
     \code{export CROSS_COMPILE=arm-linux-} \\
-    Recommended solution, but it only works inside the current
-    shell or terminal. You may put these settings in your
+    Drawback: it only works inside the current
+    shell or terminal. You could put these settings in a file
+    that you source every time you start working on the project.
+    If you only work on a single architecture with always the 
+    same toolchain, you could even put these settings in your
     \code{~/.bashrc} file to make them permanent and visible from
-    anywhere.
+    any terminal.
   \end{itemize}
 \end{frame}
 



More information about the training-materials-updates mailing list