Replicant

h1. KernelBuild

h2. Use case

Building a kernel aside Replicant, is faster to setup and faster to build since you need to fetch and use the huge Android build system.

Users wanting to add a driver to their kernel, or developers that want to work on kernel related areas can do that to speed up the development process, however if the changes are integrated back into Replicant, they will automatically be built by the Android build system, when building images.

h2. Dependencies 

Since you are not compiling any userspace applications, you don't need the Android build system. The Linux Kenrel, and Bootloaders such as uboot can be built without the Android build system.

The Trisquel ARM version of gcc seem to work well.

If you use distributions such as Parabola, this will probably not work because the arm-none-eabi-gcc is too recent for many devices kernels.

To workaround that you can install Trisquel in a container.

This way it will have very few CPU and memory overhead compared to a virtual machine.

It will also save disk space since you can just store the Trisquel rootfs in any directory.

h2. Example under Trisquel

First download the following example images:

* http://ftp-osl.osuosl.org/pub/replicant/images/replicant-4.2/0004/images/crespo/replicant-4.2-crespo.zip.asc

* http://ftp-osl.osuosl.org/pub/replicant/images/replicant-4.2/0004/images/crespo/replicant-4.2-crespo.zip

As usual, verify the signature:

<pre> gpg --verify replicant-4.2-crespo.zip.asc </pre>

<pre>

$ git clone https://git.replicant.us/replicant/kernel_samsung_crespo.git

</pre>