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

classes/populate_sdk_ext: disable signature warnings

2016-01-15T15:41:32+00:00

The user of the extensible SDK doesn't need to see these.

(From OE-Core master rev: 7045fabf73d4eef9c023edb9e0a8b8d1d3f04680)

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

classes/populate_sdk_ext: fix cascading from preparation failure

2016-01-15T15:41:32+00:00

During extensible SDK installtion, if the build system preparation step
fails we try to put something at the end of the environment setup script
to show an error when it is sourced, in case the user doesn't realise
that the partially-installed SDK is broken. However, an apostrophe in
the message (actually a single quote) appears to terminate the string
and therefore breaks the command. Drop it to avoid that.

(From OE-Core master rev: 21e591d182e24c399ae010a8eff9b89947061a46)

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

classes/populate_sdk_ext: error out of install if buildtools install fails

2016-01-15T15:41:31+00:00

If the installation of buildtools fails then we should fail the entire
installation instead of blindly continuing on.

(From OE-Core master rev: 34bb63e6c72fb862e0ef0d2b26e1bfddaf7ddb99)

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

populate_sdk_ext.bbclass: Be more permissive on the name of the buildtools

2015-12-28T07:03:15+00:00

We want to support different names for the buildtools tarball.  The
name may not always be of the default oe-core format.

For instance, at Wind River we define the built-tools name to be:

${SDK_ARCH}-buildtools-nativesdk-standalone-${DISTRO_VERSION}

because thes standard SDK_NAME has additional information that is not
relevant to the builtools tarball.

(From OE-Core master rev: b49c6f179b06a8b97106aa4c95f2cdb3c4dc0920)

Signed-off-by: Mark Hatle 
Signed-off-by: Ross Burton 
Signed-off-by: Richard Purdie

classes/populate_sdk_ext: fail if SDK_ARCH != BUILD_ARCH

2015-12-28T07:03:15+00:00

The extensible SDK relies upon uninative, and with the way that
uninative works, the build system architecture must be the same as the
SDK architecture or the extensible SDK won't be usable. At some point in
future hopefully we can remove this limitation, but until then it's
disingenuous to allow this to build, so add a check to ensure
SDK_ARCH == BUILD_ARCH and fail if it isn't.

(From OE-Core master rev: 9e30e849eda3b0a0c54d3f7ed0102760fdaef06c)

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

classes/populate_sdk_ext: tweak reporting of workspace exclusion

2015-12-28T07:03:15+00:00

If you have a local workspace layer enabled when building the
extensible SDK, we explicitly exclude that from the SDK (mostly because
the SDK has its own for the user to use). Adjust the message we print
notifying the user of this so it's clear that we're excluding it from
the SDK, and scale it back from a warning to a note printed with
bb.plain().

(From OE-Core master rev: 90f46f74a088a7b965d2205eceb9eff6f276dd38)

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

classes/populate_sdk_ext: make it clear when SDK installation has failed

2015-12-28T07:03:15+00:00

When SDK preparation fails:

* Insert an ERROR: in front of the error message
* Add an error message to the environment setup script

Hopefully this should make it more obvious when this happens.

Fixes [YOCTO #8658].

(From OE-Core master rev: 105df569b3b1982005c2edb37f4690f9ba6bde35)

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

classes/populate_sdk_ext: tidy up preparation log file writing

2015-12-28T07:03:15+00:00

Use a variable for the log file which includes the full path; this is
not only neater but avoids us writing the first part (the output of
oe-init-build-env) to a file in another directory since we are
changing directory as part of this subshell.

(From OE-Core master rev: 001af71752a9e9aab460cbd49ed049e1eb726295)

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

classes/populate_sdk_ext: detect and warn if running in OE environment

2015-10-20T09:11:44+00:00

If you run the extensible SDK environment setup script in a shell
session where oe-init-build-env has been run already, and attempt to use
the two together, strange things happen - you may not even be running
devtool from the extensible SDK, but the OE tree. This isn't a supported
use case anyway, so show a warning recommending starting a new shell
session.

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

classes/populate_sdk_ext: add note to env setup script

2015-10-20T09:11:44+00:00

Print a note at the end of the environment setup script pointing to
devtool.

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