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>
NXP's machine learning packagegroup now has a dependency for gst-shark, a GPU
profiling tool which is provided by this layer. Since it's a part of a repo
that already exists in our manifest, simply add it to the default layers of all
i.MX platforms that support the machine learning feature to be able to include
its packages out of the box.
https://onedigi.atlassian.net/browse/DEL-8551
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
ConnectCore MP15 has support to QT applications, so add it to the daily build.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
(cherry picked from commit b92028b407)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For now, we're only interested in generating the SBOM, which we can upload and
have Vigiles scan later on if needed. The report generation process adds some
overhead and can cause unwanted errors if the Vigiles server takes too long.
Enable report generation for our automated builds.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This adds two new options:
* One to generate a Vigiles CVE report along with a build
* One to include the meta-digi-security layer in a build
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Seems that 'meta-openembedded' repo does not allow shallow clones. It
fails when '--depth' option is passed:
$ git clone --depth 1 https://git.openembedded.org/meta-openembedded
Cloning into 'meta-openembedded'...
fatal: dumb http transport does not support shallow capabilities
Remove that option to allow building DEY-4.0 from GitHub repos in the
buildserver.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Support to build wayland-based graphical images has been added for ccimx93,
so build that image.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In the CC6UL this is the only image that has the connectcore demo
included, so add it to the daily build.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is dead code used in the past for the ccardimx28. It is not used in
any other platform, so just remove it.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
DEY_BUILD_PLATFORM (with correct spelling) is defined in the machine
config files, so there is no need to define it again here.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Building some packages from the ccmp15 requires the acceptance of the
STM EULA. Add the acceptance lines to the config template and fix the
path to the EULA en the mkproject script.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Framebuffer support has been removed for all platforms, however it was missing
from the ccimx6ulsbc configuration notes.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Arturo Buzarra
Javier Viguera
Gonzalo Ruiz
Gabriel Valcazar
Tatiana Leon
Mike Engel
Isaac Hermida
Francisco Gil