| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
As part of the pyro merge we need to continue to overlay these classes
in order to support vmdk.xz. While upstream has some of the underlying
required changes, we had dropped 'vmdk' as a standalone image type and
now have 'wic.vmdk' there. This was too invasive for pyro however.
This in turn means that we carry vmdk.xz support here.
Another part of this is that in some places we were checking only for
the string vmdk but also need to check for the string vmdk.xz as well.
Update these locations to use bb.utils.contains_any so that we can catch
both easily.
Bug-AGL: SPEC-899, SPEC-775, SPEC-776
Change-Id: I0cc3c06d59c97c0a76819209e313bc6f5495cc31
Signed-off-by: Tom Rini <trini@konsulko.com>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/11153
Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-boot-test: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
|
|
Currently, if you build a vmdk file, you also need to manually add in
drivers to make your image fast (vbox/vmware drivers). We can make this
automatic so that when you build a vmdk, drivers are automatically added
in. Using this approach, both vbox and vmware drivers are added, which
is more than is generally necessary, but it means that a single vmdk
image can support many use cases, and the same image can be distributed
to many developers.
For developer images, this seems like a good tradeoff because
convenience is more important than disk space/bloat for developers. For
production, we leave this option off to reduce unneeded components.
Change-Id: I8139a3ed94599c1732ea8b58bbc735c0de594234
Signed-off-by: Martin Kelly <mkelly@xevo.com>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/10219
Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
|
|
Having features allowed only during developement
of AGL is a plus. This commit allows to add tests
within recipes to check if the current build is
AGL developement. If not the build is for production.
By default, extra feature must be off.
This commits doesn't add
CPPFLAGS += "-DAGL_DEVEL"
to improve build time and cache space of yocto.
However, it is a good practice, when needed, to
use the tag AGL_DEVEL in C/C++ codes specific to
AGL and thus to include the line
CPPFLAGS_append_agl-devel = " -DAGL_DEVEL"
in recipes specific to AGL.
AGL-Bug: SPEC-594
Change-Id: Ie967a4317886ee78304999f36de5db9de22568a7
Signed-off-by: José Bollo <jose.bollo@iot.bzh>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/9393
Tested-by: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
ci-image-build: Jenkins Job builder account <agl-jobbuilder@automotivelinux.org>
Reviewed-by: Stéphane Desneux <stephane.desneux@iot.bzh>
Reviewed-by: Changhyeok Bae <changhyeok.bae@lge.com>
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
|
|
Is necessary for full-filesystem updates on a stateful system.
Bug-AGL: SPEC-440
Change-Id: I104dfbc27f05c91516d612d4c24e3533bb821d78
Signed-off-by: Anton Gerasimov <anton@advancedtelematic.com>
|
|
* Having a minimlal local.conf serving the only purpose
of user customization is the "Yocto" way of doing things
* After a source synchronization (repo sync), feature code
must be update without regenerate local.conf
Change-Id: I0bb0861f4c07a8b57cb59a03f6ffe9d2d693cbbe
Signed-off-by: Ronan <ronan.lemartret@iot.bzh>
|
Tom Rini
Martin Kelly
José Bollo
Anton Gerasimov
Ronan