From 97cd05ca25904c0344617adf191c76a4feac10ea Mon Sep 17 00:00:00 2001 From: Robert Schwebel Date: Mon, 1 Nov 2010 17:01:17 +0100 Subject: [PATCH] doc: remove obsolete link method for arch specification The cross_arch and cross_compile links method is obsolete and not available any more, so we remove it from the documentation. Signed-off-by: Robert Schwebel --- Documentation/building.dox | 14 ++++++-------- 1 file changed, 6 insertions(+), 8 deletions(-) diff --git a/Documentation/building.dox b/Documentation/building.dox index 895e9acdc..527ca45d0 100644 --- a/Documentation/building.dox +++ b/Documentation/building.dox @@ -15,19 +15,17 @@ x86_64. \todo Find out about issues on x86_64. -Selecting the architecture and the corresponding cross compiler can be -done with two methods: You can either specify it using the environment -variables @p ARCH and @p CROSS_COMPILE or you can create the soft links -cross_arch and cross_compile, pointing to your -architecture and compiler. +Selecting the architecture and the corresponding cross compiler is done +by setting the following environment variables: -\todo How to use the links? This doesn't work! +- ARCH=\ +- CROSS_COMPILE=\ For @p ARCH=sandbox we do not need a cross compiler, so it is sufficient to specify the architecture: @code -# ln -s arch/sandbox cross_arch +# export ARCH=sandbox @endcode In order to configure the various aspects of @a barebox, start the @@ -52,7 +50,7 @@ After @a barebox is configured, we can start the compilation: You can use '-j \' in order to do a parallel build if you have more than one cpus. -If everything goes well, the result is a file called @p barebox: +If everything goes well, the result is a file called @p barebox: @code # ls -l barebox