jeans/motioneyeos
jeans/motioneyeos
1
0
Fork 0
mirror of https://github.com/motioneye-project/motioneyeos.git synced 2025-07-29 14:16:31 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs/buildroot.html: cleanup trailing whitespaces

Browse Source 
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>
This commit is contained in:
Samuel MARTIN 2012-03-18 09:53:59 +01:00 committed by Peter Korsgaard
parent a0b7500352
commit 955714a0b7
1 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

24
docs/buildroot.html
View File

@ -39,22 +39,22 @@
<h2 id="about">About Buildroot</h2> <h2 id="about">About Buildroot</h2>
<p>Buildroot is a set of Makefiles and patches that allows you to easily <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 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 kernel image for your target. Buildroot can be used for one, two or all
of these options, independently.</p> of these options, independently.</p>
<p>Buildroot is useful mainly for people working with embedded systems. <p>Buildroot is useful mainly for people working with embedded systems.
Embedded systems often use processors that are not the regular x86 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 everyone is used to having in his PC. They can be PowerPC
processors, MIPS processors, ARM processors, etc.</p> processors, MIPS processors, ARM processors, etc.</p>
<p>A compilation toolchain is the set of tools that allows you to <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, 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>gcc</code>), binary utils like assembler and linker (in our case,
<code>binutils</code>) and a C standard library (for example <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.gnu.org/software/libc/libc.html">GNU Libc</a>,
<a href="http://www.uclibc.org/">uClibc</a> or <a href="http://www.uclibc.org/">uClibc</a> or
<a href="http://www.fefe.de/dietlibc/">dietlibc</a>). The system installed <a href="http://www.fefe.de/dietlibc/">dietlibc</a>). The system installed
on your development station certainly already has a compilation on your development station certainly already has a compilation
toolchain that you can use to compile an application that runs on your toolchain that you can use to compile an application that runs on your