Difference between revisions of "Build coreboot using LBdistro"

From coreboot
Jump to: navigation, search
(How to getting started?)
m (No HTML needed.)
Line 7: Line 7:
 
First you need download the toolchain used to compile some LBdistro packages:
 
First you need download the toolchain used to compile some LBdistro packages:
  
<pre>
+
wget http://lbdistro.sourceforge.net/tools/toolchain.tar.bz2
wget http://lbdistro.sourceforge.net/tools/toolchain.tar.bz2
+
</pre>
+
  
 
Extract it to /usr/local:
 
Extract it to /usr/local:
<pre>
+
 
tar jxvf toolchain.tar.bz2 -C /usr/local
+
tar jxvf toolchain.tar.bz2 -C /usr/local
</pre>
+
  
 
Get last LBdistro from SVN repository:
 
Get last LBdistro from SVN repository:
<pre>
+
 
svn co https://lbdistro.svn.sourceforge.net/svnroot/lbdistro/trunk LBdistro
+
svn co https://lbdistro.svn.sourceforge.net/svnroot/lbdistro/trunk LBdistro
</pre>
+
  
 
After that issue:
 
After that issue:
  
<pre>
+
cd LBdistro
cd LBdistro
+
make menuconfig
make menuconfig
+
make
make
+
</pre>
+
  
 
For now only QEMU compilation is generating ROM, but other boards will be added after Kdrive and application works.
 
For now only QEMU compilation is generating ROM, but other boards will be added after Kdrive and application works.

Revision as of 10:30, 14 August 2007

What is LBdistro?

LBdistro is an improvement on buildrom to let user customize what binaries will be at final ROM.

How to getting started?

First you need download the toolchain used to compile some LBdistro packages:

wget http://lbdistro.sourceforge.net/tools/toolchain.tar.bz2

Extract it to /usr/local:

tar jxvf toolchain.tar.bz2 -C /usr/local

Get last LBdistro from SVN repository:

svn co https://lbdistro.svn.sourceforge.net/svnroot/lbdistro/trunk LBdistro

After that issue:

cd LBdistro
make menuconfig
make

For now only QEMU compilation is generating ROM, but other boards will be added after Kdrive and application works.

Known problems

There is some problems when compiling it on Debian and others (on Ubuntu 6.06 it works fine). This problem will be fixed ASAP.

In my system I need change the command "lzma e" to "lzma -z" to compress payload