summaryrefslogtreecommitdiffstats
path: root/docs
diff options
context:
space:
mode:
authorSamuel MARTIN <s.martin49@gmail.com>2012-03-18 09:53:59 +0100
committerPeter Korsgaard <jacmet@sunsite.dk>2012-03-18 22:03:34 +0100
commit955714a0b7d600860ff47a47f50ea0478c6d32f2 (patch)
tree4e2e4cbb74af5925854001709ceda8d89e0c274b /docs
parenta0b75003521e695e5ac852e8aba19ca90e30ed1c (diff)
downloadbuildroot-novena-955714a0b7d600860ff47a47f50ea0478c6d32f2.tar.gz
buildroot-novena-955714a0b7d600860ff47a47f50ea0478c6d32f2.zip
docs/buildroot.html: cleanup trailing whitespaces
Signed-off-by: Samuel MARTIN <s.martin49@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
Diffstat (limited to 'docs')
-rw-r--r--docs/buildroot.html24
1 files changed, 12 insertions, 12 deletions
diff --git a/docs/buildroot.html b/docs/buildroot.html
index ddfb20a74..28aefe4f8 100644
--- a/docs/buildroot.html
+++ b/docs/buildroot.html
@@ -39,22 +39,22 @@
<h2 id="about">About Buildroot</h2>
- <p>Buildroot is a set of Makefiles and patches that allows you to easily
- generate a cross-compilation toolchain, a root filesystem and a Linux
- kernel image for your target. Buildroot can be used for one, two or all
+ <p>Buildroot is a set of Makefiles and patches that allows you to easily
+ generate a cross-compilation toolchain, a root filesystem and a Linux
+ kernel image for your target. Buildroot can be used for one, two or all
of these options, independently.</p>
- <p>Buildroot is useful mainly for people working with embedded systems.
- Embedded systems often use processors that are not the regular x86
- processors everyone is used to having in his PC. They can be PowerPC
+ <p>Buildroot is useful mainly for people working with embedded systems.
+ Embedded systems often use processors that are not the regular x86
+ processors everyone is used to having in his PC. They can be PowerPC
processors, MIPS processors, ARM processors, etc.</p>
- <p>A compilation toolchain is the set of tools that allows you to
- compile code for your system. It consists of a compiler (in our case,
- <code>gcc</code>), binary utils like assembler and linker (in our case,
- <code>binutils</code>) and a C standard library (for example
- <a href="http://www.gnu.org/software/libc/libc.html">GNU Libc</a>,
- <a href="http://www.uclibc.org/">uClibc</a> or
+ <p>A compilation toolchain is the set of tools that allows you to
+ compile code for your system. It consists of a compiler (in our case,
+ <code>gcc</code>), binary utils like assembler and linker (in our case,
+ <code>binutils</code>) and a C standard library (for example
+ <a href="http://www.gnu.org/software/libc/libc.html">GNU Libc</a>,
+ <a href="http://www.uclibc.org/">uClibc</a> or
<a href="http://www.fefe.de/dietlibc/">dietlibc</a>). The system installed
on your development station certainly already has a compilation
toolchain that you can use to compile an application that runs on your