diff options
| author |   Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-09-14 16:46:48 +1200 |
|---|---|---|
| committer | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-09-14 17:07:58 +1200 |
| commit | aaeb36e42d7366453f497a7ac68a7b1d76b5e182 (patch) | |
| tree | 3463870c3e7ca93860664e8ca04ae45c691bb49d /oe-init-build-env-memres | |
| parent | e260f0007ce3970903b9e4c1ceee34eb16b6f705 (diff) | |
| download | openembedded-core-contrib-paule/extsdk-path-fixes.tar.gz | |
lib/oe/copy_buildsystem: fix building eSDK with indirect paths in BBLAYERSpaule/extsdk-path-fixes
Indirect paths (e.g. ${TOPDIR}/../meta-something) do generally work if
used in BBLAYERS in bblayers.conf. However, if you built an extensible
SDK with this configuration then the creation of the workspace within
the SDK using devtool in do_populate_sdk_ext failed. This is because
the copy_buildsystem code was no longer correctly recognising that the
core layer ("meta") was part of a repository (e.g. openembedded-core /
poky) that should be shipped together - because of the indirection - and
thus it was splitting out the meta directory, and a number of places in
the code assume that the meta directory is next to the scripts
directory. Use os.path.abspath() to flatten out any indirections.
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Diffstat (limited to 'oe-init-build-env-memres')
0 files changed, 0 insertions, 0 deletions