| Summary: | Add support for specifying an external kernel tree | ||
|---|---|---|---|
| Product: | buildroot | Reporter: | Martin Hicks <mort> |
| Component: | Other | Assignee: | Thomas Petazzoni <thomas.petazzoni> |
| Status: | RESOLVED FIXED | ||
| Severity: | enhancement | CC: | buildroot |
| Priority: | P5 | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | All | ||
| Host: | Target: | ||
| Build: | |||
| Attachments: | external kernel tree patch | ||
Martin, I have used this a bit and it seems fine. One addition I have hacked in is an option to allow the output files to reside in the buildroot output folder using the O= option to kernel make. This allows me to have a directory containing the kernel source which does not get modified by a build and then the build files go into $(O)/build/linux-custom. If you are interested I could probably clean up my patch and submit.
>
> I have used this a bit and it seems fine. One addition I have hacked in is an
> option to allow the output files to reside in the buildroot output folder using
> the O= option to kernel make.
Yeah, good idea. If you send me a patch I'll wrap it up as one patch for Peter and repost to bugzilla.
Thanks,
mh
This bug will be fixed by the for-2011.11/pkg-infra branch which I have posted to the list. Fixed in git by Thomas/David (2690e76aa2) |
Created attachment 3079 [details] external kernel tree patch I didn't get any comments from the list, so I'm posting this here so I doesn't get lost. One thing that I changed from my original post is to conditionally create the .stamp_{downloaded,extracted,patched} files. Doing do unconditionally causes unnecessary invocation of make in the kernel directory during each rebuild. From my RFC e-mail to the buildroot list: I wanted to compile a kernel from an external git tree, so adding support for using this tree as the kernel source for buildroot seemed logical. The thing I'm seeking comments on is my short-circuiting of the .stamp_{downloaded,extraced,patched} bits. Can someone suggest a more elegant way of doing this? ..I removed patching support, since you should probably be using some other tool to manage patches in the external tree anyways. Comments appreciated