Quote:
Originally Posted by NiLuJe
The patch doesn't touch the config/defconfig right now, but you could certainly do so, although I'm not familiar with buildroot's kernel build procedure, so I'm not sure what's the best way to achieve that...
|
For kernel building, Buildroot tries to be everything to everybody.
But it is easy to get lost in the details.
The most practical way(s):
Build the kernel outside of Buildroot, set Buildroot to use the "external custom kernel" (or words to that effect).
That is how most of the developers claim that they use it in their "day job". Many of the lead developers are using Buildroot in their "day job" to produce embedded systems under contract.
The next most practical way(s):
Open the kernel archive, apply all patches and changes desired, create a new "local" kernel archive.
Then tell Buildroot to use that local archive file.
The situation is similar to that of the cross-tool-chain - -
Buildroot **will** build that, but in commercial production use, that is rarely the common practice.
Same, same with the Linux kernel. In commercial production use, the kernel is built (as a separate build project) outside of the Buildroot system.
The reason for both are the same - once built and working as intended, it is very rare to change either of them during a product's lifetime.
(And it saves a tremendous amount of Q.A. testing to not have to repeat that for the tool chain and kernel.
Note: Running the target binary "tests" (make check) is not currently supported by Buildroot.)