openembedded-core.git/meta/classes/populate_sdk_ext.bbclass, branch master-next2

classes/populate_sdk_ext: work around runqemu behaviour within the eSDK

2017-04-19T09:38:31+00:00

Currently, in order to figure out variable values when run within the
eSDK, runqemu does not use the standard SDK method nor is it able to run
bitbake (since the eSDK environment isn't initialised like the normal
OE build environment). runqemu really ought to be fixed, but the quick
workaround is to set DEPLOY_DIR_IMAGE in the environment so that runqemu
can find image files.

Fixes [YOCTO #10447].

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

populate_sdk_ext: Add do_addto_recipe_sysroot to BB_SETSCENE_ENFORCE_WHITELIST

2017-04-14T08:46:11+00:00

Without this, eSDK builds are failing due to qemu-helper-native's dependency on this
task. It makes sense to allow this to execute in eSDK contexts (its a non-sstate task
intentionally).

Signed-off-by: Richard Purdie

classes/populate_sdk_ext: reset TCLIBCAPPEND to get consistent TMPDIR

2017-04-13T22:57:38+00:00

populate_sdk_ext sets TMPDIR to a known static value with '/tmp' directory
name and that name is hard coded in a few places (e.g., in
meta-environment-extsdk.bb that writes the eSDK environment variables).

Distros that do not reset TCLIBCAPPEND (poky does) end up getting
TMPDIR = /tmp-${TCLIBCAPPEND} via defaultsetup.conf and that breaks
the functionality in eSDK that expects everything is in /tmp.

To get TMPDIR consistent, we also need to reset TCLIBCAPPEND in
populate_sdk_ext.bbclass.

Fixes: [YOCTO #11298]

Signed-off-by: Mikko Ylinen 
Signed-off-by: Richard Purdie

populate_sdk_ext.bbclass: enhance compatibility with rm_work.bbclass

2017-03-30T09:04:06+00:00

"bitbake -c populate_dsk_ext" must not trigger do_rm_work, because it
is impossible to declare that the additional tasks activated by "-c
populate_dsk_ext" must run before do_rm_work. When do_populate_dsk_ext
and do_rm_work are both active, the resulting race condition breaks
do_populate_dsk_ext.

The existing bitbake dependencies can't be used for that, because
"addtask populate_dsk_ext before do_rm_work" would then always execute
populate_dsk_ext also in normal builds.

do_populate_dsk_ext triggers do_rm_work indirectly through the
dependency on do_build of the SDK_TARGETs. Using the new
do_build_without_rm_work instead (when available, with do_build as
before if not) avoids the problem.

However, one has to be careful to not trigger do_rm_work in the same
build in some other way.  "bitbake core-image-sato:do_populate_sdk_ext
core-image-sato:do_build" still fails, for example. Doing one after
the other works.

Fixes: [YOCTO 11042]

Signed-off-by: Patrick Ohly 
Signed-off-by: Richard Purdie

populate_ext_sdk: Merge auto.conf into local.conf

2017-03-03T11:15:22+00:00

auto.conf is included before local.conf. Instead of keeping them separate, merge
them into the extsdk local.conf. As it happens we can do this quite neatly, more
neatly than the current code IMO and it makes the configuration easier for the end
user to understand too.

This means auto.conf is then available for the testsdk code to use for testing
purposes.

Signed-off-by: Richard Purdie

populate_ext_sdk: Append to SSTATE_MIRRORS

2017-03-03T11:15:21+00:00

We need to appent to SSTATE_MIRRORS in case other areas of code are also
setting the variable.

Signed-off-by: Richard Purdie

populate_sdk_ext: Allow generation of meta-extsdk-toolchain even for minimal SDKs

2017-03-01T16:11:40+00:00

If you build a minimal eSDK currently, you don't build meta-extesdk-toolchain
even if you will have built most of its dependencies. This means when you try
and install a toolchain into the eSDK, it fails, breaking our automated testing
of the eSDK.

Therefore add the dependency unconditionally even when a minimal eSDK is being
built and allow the automated testing to work.

Signed-off-by: Richard Purdie

classes: Drop now unneeded update_data calls

2017-02-15T17:29:41+00:00

Now that the datastore works dynamically we don't need the update_data calls
so we can just remove them. They're not actually done anything at all for
a while.

Signed-off-by: Richard Purdie

classes/populate_sdk_ext: account for custom image tasks

2017-02-07T14:48:55+00:00

Any custom tasks that were added on the image between do_image_complete
and do_build were not being taken into account. Use the newly added
bb.build.tasksbetween() function to take care of that.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie

classes/populate_sdk_ext: remove unnecessary dependencies breaking SDK_TARGETS

2017-02-07T14:48:55+00:00

Up until recently it was possible to set SDK_TARGETS to include a native
recipe you wanted installed into the sysroot when installing the eSDK.
I'm not sure what happened but now when you try to add a native recipe
to SDK_TARGETS you get a missing task error because this recipe has no
do_package_write_* task. Of course such a task dependency is erroneous
and is apparently caused by setting SDK_RDEPENDS. I've checked and it
turns out that we no longer need to set SDK_RDEPENDS anyway (probably
because we explicitly set up task dependencies further down in the
class, which I don't think we were fully doing in early versions of the
eSDK). Thus, drop setting this variable to restore the functionality.

Signed-off-by: Paul Eggleton 
Signed-off-by: Richard Purdie