Difference between revisions of "Bering-uClibc 7.x - Developer Guide - Providing kernel headers"
From bering-uClibc
| Line 11: | Line 11: | ||
The kernel headers are a requirement to build the toolchain. | The kernel headers are a requirement to build the toolchain. | ||
The command | The command | ||
| + | |||
<code class="filename">./buildtool.pl headers linux</code> | <code class="filename">./buildtool.pl headers linux</code> | ||
| − | builds those headers in the directory <code class="filename">headers</code> in the buildtool root directory and creates a link in <code class="filename">repo/ | + | |
| + | builds those headers in the directory <code class="filename">headers</code> in the buildtool root directory and creates a link in <code class="filename">repo/toolchain/linux-headers</code>. | ||
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. | As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete. | ||
Revision as of 18:51, 2 October 2019
| Providing kernel headers | ||
|---|---|---|
| Prev | Bering-uClibc 7.x - Developer Guide | Next |
Building the kernel headers tarball is different from building all other Packages.
The kernel headers are a requirement to build the toolchain. The command
./buildtool.pl headers linux
builds those headers in the directory headers in the buildtool root directory and creates a link in repo/toolchain/linux-headers.
As we are moving away from the tarball code containers to a true git environment creating these tarballs has become obsolete.
Please note, that toolchains can support different kernel versions, which may be useful especially in transitions to a newer versions, where not all toolchains will be supported immediately. It is advised to keep the kernel headers for the oldest kernel a toolchain uses.
| Prev | Up | Next |
