From: Robert Schwebel <r.schwebel@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 01/13] doc: remove obsolete link method for arch specification
Date: Tue, 2 Nov 2010 14:10:30 +0100 [thread overview]
Message-ID: <1288703442-5032-2-git-send-email-r.schwebel@pengutronix.de> (raw)
In-Reply-To: <1288703442-5032-1-git-send-email-r.schwebel@pengutronix.de>
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>
---
Documentation/building.dox | 14 ++++++--------
1 files changed, 6 insertions(+), 8 deletions(-)
diff --git a/Documentation/building.dox b/Documentation/building.dox
index 895e9ac..527ca45 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
-<i>cross_arch</i> and <i>cross_compile</i>, 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=\<architecture>
+- CROSS_COMPILE=\<compiler-prefix>
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 \<n\>' 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
--
1.7.2.3
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-11-02 13:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-02 13:10 documentation updates Robert Schwebel
2010-11-02 13:10 ` Robert Schwebel [this message]
2010-11-02 13:10 ` [PATCH 02/13] doc: unify documentation for 'loadenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 03/13] doc: remove ..., confuses doxygen Robert Schwebel
2010-11-02 13:10 ` [PATCH 04/13] doc: unify documentation for 'mount' Robert Schwebel
2010-11-02 13:10 ` [PATCH 05/13] doc: unify documentation for 'printenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 06/13] doc: unify documentation for 'protect' and 'unprotect' Robert Schwebel
2010-11-02 13:10 ` [PATCH 07/13] doc: unify documentation for 'saveenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 08/13] doc: unify documentation for 'setenv' Robert Schwebel
2010-11-02 13:10 ` [PATCH 09/13] doc: remove sh from command documentation Robert Schwebel
2010-11-02 13:10 ` [PATCH 10/13] doc: unify documentation for 'linux16' Robert Schwebel
2010-11-02 13:10 ` [PATCH 11/13] doc: put CPUIMX35 into the right chapter Robert Schwebel
2010-11-02 13:10 ` [PATCH 12/13] doc: put babage board " Robert Schwebel
2010-11-02 13:10 ` [PATCH 13/13] doc: put cupid " Robert Schwebel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1288703442-5032-2-git-send-email-r.schwebel@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=barebox@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox