Packagegroups define sets of packages to be installed in the rootfs
*depending* on the hardware variant (~MACHINE_FEATURES). For example
installing or not the bluetooth firmware depending on machine variant
having bluetooth.
It may happen that we build sequentially machines with different
features using the same sstate and thus it may happen we end with a
rootfs lacking bluetooth firmware for a bluetooth variant.
So add all packagegroups to the list of packages to purge state-cache
between platform builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed so jenkins jobs not using 'meta-digi-dey' (the layer
containing the cleaned recipe) can complete. Otherwise they fail with:
ERROR: Nothing PROVIDES 'packagegroup-dey-examples'
(for example using just the BSP layer 'meta-digi-arm' with standard
image recipes, e.g. core-image-minimal)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In the buildserver we share the state-cache for all the different
platforms we build in a jenkins job. This may cause problems with
some packages that have different runtime dependencies depending on
the platform or variant.
Purge then the state-cache of those problematic packages between
platform builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For daily builds just copy the firmware images to avoid running out of
space in the buildserver.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to build 'core-image-minimal' or 'core-image-sato' standard
images using only the BSP layer meta-digi-arm.
https://jira.digi.com/browse/DEL-547
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This will allow to remove the packages working directories to save disk
space.
https://jira.digi.com/browse/DEL-521
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The final product will be called "Digi Embedded for Yocto" or DEY for
short.
This commit renames all relevant files.
https://jira.digi.com/browse/DEL-474
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
If TEMPLATECONF is set in the environment, we will add the platform to
the path so that it's possible to use specific template configurations
for different platforms in the build server.
https://jira.digi.com/browse/DEL-497
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This allows to build for all supported distributions:
del (del-image-minimal)
del-gui (del-image-graphical
poky (core-image-minimal etc.)
dbl (dbl-image-base)
https://jira.digi.com/browse/DEL-481
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This will allow to compile del-image-graphical or any of the other standard
Yocto image targets as meta-toolchain, meta-toolchain-sdk, adt-installer,
or meta-ide-support.
https://jira.digi.com/browse/DEL-476
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>