If a previously existing workspace is missing some repos due to "repo sync"
errors, any builds re-using that workspace will fail silently when attempting
to run "git clean -fdx" on all repos via "repo forall".
Ignore missing repos to prevent these situations.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Default value of 'MKP_CONFIGPATH' points to a config path in the
meta-digi/meta-digi-arm layer.
When mkproject.sh is called with the '-m' argument, another layer is
provided to build the project from. In this layer the conf/templates
new structure must be respected, but it is likely it does not contain a
meta-digi-arm directory on top.
Keep the 'meta-digi-arm' directory in the config path by default, but
remove it when a different layer is provided through an argument.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
* generate SD card image using wic
* remove ZIP_INSTALLER_CFG since DEY_IMAGE_INSTALLER="1" is now the default
* drop purge_sstate
https://onedigi.atlassian.net/browse/DEL-9768
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Define YOCTO_SSTATE_DIR honoring DY_SSTATE if configured in Jenkins,
otherwise use the previous default value.
While on it, quote YOCTO_INST_DIR expansion to prevent word splitting.
https://onedigi.atlassian.net/browse/DEL-9762
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit enables building dey-image-flutter for the ConnectCore MP15
platform. It integrates the necessary configurations to support Flutter-based
graphical applications on this platform.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The CC6UL SOM doesn't support booting from the SD card.
The STM based SOMs use a wic template to generate the SD card
image.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The generation of the sdcard image takes time and resources, and
it's not involved in the Get Started.
This can be easily re-enabled by appending the variable in the
project local.conf.
Append the variable in the build scripts, to facilitate its usage
on release builds.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
The CCMP1 platforms were integrated as part of DEY-5.0, and this commit
restores their support in the mkproject build system.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The release build should ensure it starts from a fresh environment to avoid
potential mismatches with old code.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
We need separate config files for different DEY versions, so store each file
set in a folder named after the corresponding Yocto codename.
https://onedigi.atlassian.net/browse/DEL-9539
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Instead of having one toolchain per image, we now provide one per platform.
https://onedigi.atlassian.net/browse/DEL-9297
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Starting in poky commit 8791c77a4098d62080ecad09d94718eccd7f1a47, there is
now a check to make sure TEMPLATECONF follows specific rules. If we don't abide
by them, an error will occur when creating a project with our mkproject.sh
script. Move the templates to the place they're supposed to be in and reflect
the change in mkproject.sh.
https://onedigi.atlassian.net/browse/DEL-9011
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Qt5/Qt6 and Webkit layers are specifically for functionality related with GUIs,
which aren't available for these platforms. For the moment, leave meta-webkit
in the ccimx91's bblayers, since our dynamic selinux layer has a spurious
dependency with our dey-image-webkit recipe.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commits adds the CCMX91 platform to the DEY
build system. Furthermore, it creates generic ccimx9
support to be used for the CCiMX91 and CCiMX93
platform.
https://onedigi.atlassian.net/browse/DEL-9106
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
We have intermittent build failures due to fetch errors of some large
source packages (like linux.git).
This commit tries to workaround those failures by downloading all the
source packages, with a retries mechanism, before starting the build.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In our previous commit, we changed the CVE scan class from "vigiles" to
"digi_ccss" if we plan on building images with the CVE layer. However, we
make this change in conf/local.conf and then run "bitbake-layers add-layer" to
add said layer. Since the bbclass is exclusive to the CVE layer, bitbake isn't
able to recognize it and fails.
Add the CVE layer to the project before adding the Vigiles configuration
template to conf/local.conf.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Our CVE layer now includes a new bbclass that extends the logic of the
"vigiles" bbclass. Use this new class if we are building images with the CVE
layer.
https://onedigi.atlassian.net/browse/DEL-8939
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
The crank engine hasn't been fully tested on these platforms yet, so remove
the image from our default build.
https://onedigi.atlassian.net/browse/DEL-8862
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
LVGL graphical library has support for different backends, in the case of the
ccimx6ul we use the fbdev directly, so we don't need the x11 support.
This commit removes x11 support for the ccimx6ul platform for the
dey-image-lvgl image.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
LVGL is a free and open-source embedded graphics library that is able to run
in environments with limited resources.
This image includes a desktop environment and an LVGL widget demo (lvgl_demo)
https://onedigi.atlassian.net/browse/DEL-8740
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
DY_MACHINES_LAYER is an optional variable only used once. Use bash's
"alternate value" expansion and get rid of the intermediate MACHINES_LAYER
variable.
While on it, remove the DY_BUILD_VARIANTS reference in the script header
as that was removed long ago.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
DY_MANIFEST parameter allows to do a 'repo init' with a specific
manifest file contained in the manifest repository. For example,
'manufacturing.xml' for building manufacturing projects.
By default no manifest file parameter is provided, so the 'repo init'
command will initialize based on the 'default.xml' manifest file.
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
(cherry picked from commit c38b4fc4f2c565ab9db20c082016401341e78ce5)
This layer provides machine learning functionality, so include it in our
default layers so customers can use it out of the box if wanted.
https://onedigi.atlassian.net/browse/DEL-8551
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Javier Viguera
Gabriel Valcazar
Hector Palacios
Gonzalo Ruiz
Arturo Buzarra
Isaac Hermida
Mike Engel