Commit cec43a8f authored by Maxime Hadjinlian's avatar Maxime Hadjinlian Committed by Thomas Petazzoni
Browse files

website: new website !



A new menu and logo for the website, also some of the contents has been
reworked.

This patch also removes files that are no longer used, like the old
stylesheet and a few pages. The content of theses pages has mostly been
merged in other pages or was redudant with the manual.

[Thomas: integrate a few typo fixes noticed by Thomas De
Schampheleire]

Signed-off-by: default avatarMaxime Hadjinlian <maxime.hadjinlian@gmail.com>
Signed-off-by: default avatarThomas Petazzoni <thomas.petazzoni@free-electrons.com>
parent 39b26d71
Loading
Loading
Loading
Loading
+1 −10
Original line number Diff line number Diff line
<!--#include file="header.html" -->


<!-- Begin Introduction section -->

<h3>Buildroot: making Embedded Linux easy</h3>

<div align="center">
<a href="images/menuconfig.png">
 <img src="images/menuconfig_small.png" width="340" height="220"
 alt="Buildroot menuconfig" border="0">
</a>
  <img src="images/menuconfig.png" width="340" height="220" alt="Buildroot menuconfig" border="0">
</div>

<p>Buildroot is a set of Makefiles and patches that makes it easy to
@@ -60,5 +52,4 @@ cross-compilation process.</p>
GENERAL PUBLIC LICENSE V2 (Or later)</a>. Stable releases are
delivered every three months.</p>


<!--#include file="footer.html" -->

docs/contribute.html

0 → 100644
+39 −0
Original line number Diff line number Diff line
<!--#include file="header.html" -->

<h2>Contribute</h2>

Buildroot is an open source project and if you want to contribute, here a few
pointers to get you started.

<p>Don't forget to look at <a href="./support.html">Support</a> if you need any
help.
And thanks for your help !</p>

<h3>Autobuilders</h3>

The <a href="http://autobuild.buildroot.org/">Autobuilders</a> are used to test
Buildroot with a lot of differents settings (toolchains, various packages, etc)
on all the supported platforms.

<p>But despite our best effort, sometimes it fails.</p>
<p>That's where you can help ! Look at a package that fails and try to fix it !</p>

<h3>Wiki</h3>

Have a look at the <a href="http://elinux.org/Buildroot">eLinux Wiki</a> a todo
list is available there, which can help you find out what you could do to help
Buildroot.

<h3>Patchwork</h3>

<a href="http://patchwork.ozlabs.org/project/buildroot/list/">Patchwork</a>
is a patch tracking system, if you submit a patch, it will appear here.

<p>You can have a look at a patch that interests you and test it on your machine,
if it succeeds, you can send a <a
  href="http://buildroot.org/downloads/manual/manual.html#_reviewing_testing_patches">"Tested-by"</a>,
if it fails, you can also send a mail on the <a
  href="http://buildroot.org/downloads/manual/manual.html#_mailing_list">mailing
  list</a> and report what has happened to you.</p>

<!--#include file="footer.html" -->

docs/developer.html

deleted100644 → 0
+0 −47
Original line number Diff line number Diff line
<!--#include file="header.html" -->


<h3>Developer Access</h3>

Because we use Git for version control, you don't need developer (ssh)
access on uclibc.org to contribute to Buildroot, but you can request
it if needed.

<p>

To obtain developer access, you will need to demonstrate you are
serious by submitting a few good patches first.  Then, you will need
to select a username to use when logging in, you will need to send me
the username you have selected, you must send me your preferred
contact email address, and finally, you must send me an ssh version 2
DSA key with 1024 bits (the default) or more.  If you do not currently
have an ssh version 2 DSA key, you can generate a key using the
command<pre>ssh-keygen -t dsa</pre> This will create the
files <pre>/home/&lt;USERNAME&gt;/ssh/id_dsa
/home/&lt;USERNAME&gt;/.ssh/id_dsa.pub</pre> It is recommended that
you generate a key with a "passphrase" for security reasons.

<p>
Make the file known to the system by running

<pre>ssh-add ~/.ssh/id_dsa</pre>

You must then send the content of 'id_dsa.pub' to me so I can setup your account.
The content of 'id_dsa' should of course be kept secret.

<p>

Once you have an account, you can use it to store Git
repositories. Simply put them in subdirectories of your ~/git, and
touch ~/git/<repo>/git-daemon-export-ok, after which the hourly
cronjob will pick them up and show them in cgit. They are also
available though git-daemon:

<pre>git clone git://git.buildroot.net/~&lt;USERNAME&gt/git/&lt;REPO&gt;</pre>

For additional detail on how to use Git, please visit the
<a href="http://git-scm.org/">the Git website</a>.

<!--#include file="footer.html" -->

+2 −2
Original line number Diff line number Diff line
<!--#include file="header.html" -->

<h3>Documentation</h3>
<h2>Documentation</h2>

<p>The Buildroot user manual is where you want to start reading if you
wish to understand how Buildroot works, or wish to change/extend/fix
@@ -28,7 +28,7 @@ help:</p>

<ul>

  <li>On the <a href="lists.html">buildroot mailing list</a>
  <li>On the <a href="support.html">buildroot mailing list</a>
  at <code>buildroot at uclibc.org</code></li>

  <li>On the <a href="irc://freenode.net/#buildroot">Buildroot IRC
+40 −5
Original line number Diff line number Diff line
<!--#include file="header.html" -->



<h3>Download</h3>
<h2>Download</h2>

<p>

@@ -43,8 +41,45 @@ follow development, but cannot or do not wish to use Git.
	<li> Click here to <a href="http://git.buildroot.net/buildroot">browse the source tree</a>.
	</li>

	<li>Anonymous <a href="git.html">Git access</a> is available.
	</li>
</ul>


<h2>Repository</h2>

The buildroot repository can be browsed online through cgit at
<a href="http://git.buildroot.net/buildroot/">http://git.buildroot.net/buildroot</a>.
To grab a copy of the repository use

<pre>
git clone git://git.buildroot.net/buildroot</pre>

Or if you're behind a firewall blocking git:

<pre>
git clone http://git.buildroot.net/git/buildroot.git</pre>

<p>

Please use the native git protocol if at all possible, as it's a lot
more efficient than HTTP.

<p>

If you are not already familiar with using Git, we recommend you visit <a
href="http://git-scm.org">the Git website</a>.

<p>

Once you've checked out a copy of the source tree, you can update your source
tree at any time so it is in sync with the latest and greatest by entering your
buildroot directory and running the command:

<pre>
git pull
</pre>

Because you've only been granted anonymous access to the tree, you won't be
able to push your changes to the repo. Changes can instead be submitted for
inclusion by posting them to the buildroot mailing list.

<!--#include file="footer.html" -->
Loading