9
0
Fork 0

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 <r.schwebel@pengutronix.de>
This commit is contained in:
Robert Schwebel 2010-11-01 17:01:17 +01:00
parent f0e62e69a5
commit 97cd05ca25
1 changed files with 6 additions and 8 deletions

View File

@ -15,19 +15,17 @@ x86_64.
\todo Find out about issues on x86_64. \todo Find out about issues on x86_64.
Selecting the architecture and the corresponding cross compiler can be Selecting the architecture and the corresponding cross compiler is done
done with two methods: You can either specify it using the environment by setting the following environment variables:
variables @p ARCH and @p CROSS_COMPILE or you can create the soft links
<i>cross_arch</i> and <i>cross_compile</i>, pointing to your
architecture and compiler.
\todo How to use the links? This doesn't work! - ARCH=\<architecture>
- CROSS_COMPILE=\<compiler-prefix>
For @p ARCH=sandbox we do not need a cross compiler, so it is sufficient For @p ARCH=sandbox we do not need a cross compiler, so it is sufficient
to specify the architecture: to specify the architecture:
@code @code
# ln -s arch/sandbox cross_arch # export ARCH=sandbox
@endcode @endcode
In order to configure the various aspects of @a barebox, start the 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 \<n\>' in order to do a parallel build if you have more You can use '-j \<n\>' in order to do a parallel build if you have more
than one cpus. 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 @code
# ls -l barebox # ls -l barebox