[OE-core] SDK confusion!

[Bjørn Forsman]

On 17 December 2012 20:58, Bjørn Forsman <bjorn.forsman at gmail.com> wrote:
> Hi Mark,
>
> On 17 December 2012 16:40, Mark Hatle <mark.hatle at windriver.com> wrote:
>> On 12/17/12 9:31 AM, Bjørn Forsman wrote:
>>> Hi,
>>>
>>> I'm really confused about how to use/customize the generated SDK in
>>> openembedded. I've spent two days messing around with angstrom
>>> setup-scripts, poky and yocto and now I really need help.
> [...]
>> In oe-core with the branch tag 'denzil' or the master, there are two ways of
>> generating an SDK.
>>
>> The first (which is also present in the older oe-core systems) uses a
>> specific SDK recipe.  For instance, meta-toolchain.  This recipe simply
>> makes the toolchain elements available to you and you need to provide the
>> necessary sysroot for your SDK.  An alternative is something like
>> meta-toolchain-gmae which provides a specific set of sysroot components for
>> the 'gnome mobile applicable environment.'
>>
>> The advantage of this first way is it allows a product designer to release a
>> targeted SDK for their application developers.  You don't have to put
>> everything that will end up on the target image into the SDK, only the
>> libraries, headers and interfaces that an app developer are allowed to use.
>>
>> The second way (which is newer) is the ability to generate an SDK based on
>> the contents of the image.  This uses a new task called "populate_sdk" that
>> can be run with any image recipe, i.e. "bitbake core-image-minimal -c
>> populate_sdk". This will generate an SDK image that includes the software
>> from the image, in addition to related -dev and -dbg packages.
>>
>> The advantage of this second way is that you have an SDK that enables
>> developing for the contents of the image, as well as system wide
>> cross-debugging with the -dbg packages.
>>
>> The items below are specific to one packaging system, opkg.  The items above
>> are generic and are expected to work in any of the supported methods.
>
> Thank you very much!
>
> "bitbake <image-name> -c populate_sdk" is exactly what I want. Brilliant!

Hm, that didn't work so well for me:

bfo at mini:~/setup-scripts [git::master]$ bitbake console-image -c populate_sdk
Loading cache: 100%
|########################################################################################################################################################################|
ETA:  00:00:00
Loaded 2858 entries from dependency cache.

OE Build Configuration:
BB_VERSION        = "1.15.2"
TARGET_ARCH       = "arm"
TARGET_OS         = "linux-gnueabi"
MACHINE           = "beaglebone"
DISTRO            = "angstrom"
DISTRO_VERSION    = "v2012.05"
TUNE_FEATURES     = "armv7a vfp neon cortexa8"
TARGET_FPU        = "vfp-neon"
meta-angstrom     =
"angstrom-v2012.05-yocto1.2:4e15bc5f06ae3c5ad3df1b32a304a4a4c384e788"
meta-oe
toolchain-layer
meta-efl
meta-gpe
meta-gnome
meta-xfce
meta-initramfs    = "denzil:e77646bc2cf905fd671fc5c19ab6fd17f9b94b3f"
meta-opie         = "master:efa3892b20a4ef80274e56e5633ebd62c16f9731"
meta-java         = "master:3386ea6c96096f107f43f282f654e5afa456109e"
meta-browser      = "master:c47f59df2e723495679c751cbdf6a8c6adec4b6a"
meta-mono         = "master:83f8233b0498aadb18bf7605c3ba6c71d9e13a3a"
meta-kde          = "master:5b0882d951cfd71886d423c190faaa7c7f932333"
meta-ti           =
"angstrom-staging-yocto1.2:edfd9649cbd16b2cdb5385954c0441c7bba92f8d"
meta-efikamx      = "master:2c09a3a780b23448e8a6ca964256ff7f5ccba65d"
meta-nslu2        = "master:3d9fc951b05b4df476374b6fc3085ebac7f293ee"
meta-htc
meta-nokia
meta-openmoko
meta-palm         = "master:2b106be01228f64298d6cb338f93088806594344"
meta-handheld     = "master:1f05a15aceb4c3a19fa070463b58125b5658b2a9"
meta-raspberrypi  = "denzil:34eef2ea4f5f24630dbb73b386861430167b8431"
meta-intel
meta-sugarbay
meta-crownbay
meta-emenlow
meta-fishriver
meta-fri2
meta-jasperforest
meta-n450         = "master:f75f9b6f68473eb0efac802409608f8389be0030"
meta              = "denzil:d35560f33f257bd12a07c7c0be770319086d6ad9"

NOTE: Resolving any missing task queue dependencies
NOTE: Preparing runqueue
ERROR: Task do_populate_sdk does not exist for target console-image

Summary: There was 1 ERROR message shown, returning a non-zero exit code.
bfo at mini:~/setup-scripts [git::master]$


Suggestions?

Best regards,
Bjørn Forsman