Add dependency on kernel headers
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 10 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 10 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [Buildroot] [PATCH 0/10] Add dependency on kernel headers
Hello All!
On 2014-02-16 18:27 +0100, Yann E. MORIN spake thusly:
Quoted 17 lines
This series introduces infrastructure for packages to depend on the required version of kernel headers.
It follows the proposal made on the list:
http://lists.busybox.net/pipermail/buildroot/2014-February/088924.htmlThe basic idea is to add a symbol for each kernel header version, and have toolchains select the appropriate symbol, and packages depend on the appropriate symbol.
In this series:
- such symbols are added for all kernel headers >= 3.0;
- the internal toochain backend selects the appropriate symbol
without user-visible changes;
Quoted 8 lines
- the predefined external toolchains select the appropriate symbols without user-visible changes; those using kernel headers older than 3.0, select nothing, and a comment is added to state so;
- for the custom external toolchain, a new choice is shown to the
user, to select the appropriate kernel headers version;- five packages are converted to take advantage of this.
There is one thing this series does not do: ensure the selection is correct, by way of a new 'check_headers_version' herlper in toolchain/helpers.mk.
This can be added later, or in a second iteration of the series, if need be.
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'