From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Benjamin Fleming <bfleming@meteorcomm.com>,
Andre McCurdy <armccurdy@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: populate_sdk and kernel headers
Date: Wed, 8 Jul 2015 13:19:43 -0400 [thread overview]
Message-ID: <559D5BAF.4020008@windriver.com> (raw)
In-Reply-To: <12506c4bd3d74f129ccf68753b0b280c@MCCRENEX01.meteorcomm.lan>
On 2015-07-08 1:05 PM, Benjamin Fleming wrote:
> Ok,
> adding kernel-devsrc to my IMAGE_INSTALL caused the kernel source to be included in the SDK. Unfortunately, it is now also included in the target image.
> I found adding kernel-devsrc instead to TOOLCHAIN_TARGET_TASK gave me what I wanted (/usr/src/kernel in the SDK but NOT in the target image)
>
> Also, I really only need the kernel headers (similar to the linux-headers packages in Ubuntu) for developing out-of-source kernel modules. Is there is a different package I should be using?
>
The linux-libc-headers are the uapi exported headers, but as for the
source for module builds, it is currently unified in the
kernel-devsrc package.
We have a long history with the packaging of the sources, and what
to export where .. and even the ordering of that packaging. So while
splitting out the headers may seem simple, it requires a bit more
finesse of getting the headers, the right amount of script and Kbuild
support to get it exactly right.
By keeping the two together, we ensure that we have enough to meet
all development tasks.
There are some enhancements for this in flight for the 1.9 release, so
it is something that we are considering .. just keeping those existing
use cases and workflows from breaking is the sticky part.
Cheers,
Bruce
> Thanks,
> Ben
>
>> -----Original Message-----
>> From: Andre McCurdy [mailto:armccurdy@gmail.com]
>> Sent: Tuesday, July 07, 2015 5:54 PM
>> To: Benjamin Fleming
>> Cc: yocto@yoctoproject.org
>> Subject: Re: [yocto] populate_sdk and kernel headers
>>
>> On Tue, Jul 7, 2015 at 4:16 PM, Benjamin Fleming
>> <bfleming@meteorcomm.com> wrote:
>>> Hello,
>>> I want my kernel headers to be included in the SDK output when I run
>> bitbake myimage -c populate_sdk. I expect to see the headers in my installed
>> SDK folder such as <sdk>/sysroot/<target_mach>/usr/src/kernel; however, I
>> don't see anything there. Also, I don't want the headers appearing on the
>> target.
>>>
>>> In my recipe I have added IMAGE_INSTALL += kernel-modules, and
>>> SDKIMAGE_FEATURES += kernel-devsrc. The kernel I'm using is
>>> linux-altera-ltsi-rt from
>>> https://github.com/kraj/meta-altera/blob/master/recipes-kernel/linux/l
>>> inux-altera-ltsi-rt_3.10.bb
>>> What am I missing?
>>
>> Try adding kernel-devsrc to IMAGE_INSTALL rather than
>> SDKIMAGE_FEATURES.
>>
>>> Thanks,
>>>
>>> Ben
>>> --
>>> _______________________________________________
>>> yocto mailing list
>>> yocto@yoctoproject.org
>>> https://lists.yoctoproject.org/listinfo/yocto
next prev parent reply other threads:[~2015-07-08 17:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-07 23:16 populate_sdk and kernel headers Benjamin Fleming
2015-07-08 0:53 ` Andre McCurdy
2015-07-08 17:05 ` Benjamin Fleming
2015-07-08 17:19 ` Bruce Ashfield [this message]
2015-07-08 17:52 ` Benjamin Fleming
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=559D5BAF.4020008@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=armccurdy@gmail.com \
--cc=bfleming@meteorcomm.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.