**** BEGIN LOGGING AT Fri Dec 27 02:59:58 2013 Dec 27 04:41:06 Hello folks Dec 27 04:41:22 Happy holidays for everyone ... Dec 27 04:42:02 Does anyone ever used git-annex with OE? **** BEGIN LOGGING AT Fri Dec 27 06:01:12 2013 Dec 27 13:04:01 I create my SDK with "bitbake -c populate_sdk ". But I have to manually add the "kernel-dev" package to my image in order to get the kernel src in the SDK, so that I can develop kernel modules with it. Is there a cleaner way of getting the kernel src in the SDK ? Of course I don't want the kernel-src in the image itself Dec 27 15:19:04 jkroon_: there are variables that control the host and target packages to be installed into the sdk. iirc they're near the top of package_sdk.bbclass or so Dec 27 15:19:22 * kergoth admittedly hasn't looked at that code in a while though Dec 27 15:44:19 kergoth, thanks. nothing obvious sticks out to me though Dec 27 15:45:28 jkroon_: found it, see lines 10-13 of populate_sdk_base.bbclass, and lines 5-7 of image.bbclass. Dec 27 15:45:58 jkroon_: as you can see, it obeys TOOLCHAIN_{HOST,TARGET}_TASK. the target one defaults to PACKAGE_INSTALL, which comes from IMAGE_INSTALL, when using populate_sdk for an image Dec 27 15:46:21 so to add something else, simply add TOOLCHAIN_TARGET_TASK += "some-other-package" to your image recipe after the inherit of image Dec 27 15:46:32 that is, to add something else just to the sdk for the image, not to the image itself Dec 27 15:46:38 you could hack it from local.conf with overrides also Dec 27 15:46:54 kergoth, many thanks Dec 27 15:47:06 np Dec 27 15:47:46 I really should learn more recipe hacking Dec 27 15:48:47 in this case, we know that all images support populate_sdk, and the only class in common to all images is image.bbclass, so you can start by examining that to see how the images are constructed. then at the top of that, you can see it pulls in populate_sdk_base **** ENDING LOGGING AT Sat Dec 28 02:59:58 2013