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>
This layer has no effect unless "selinux" is in the DISTRO_FEATURES, so it's
safe to add it to our default builds.
https://onedigi.atlassian.net/browse/DEL-7641
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
By default is enabled the reproducible builds feature and to provide a real
timestamp for the build system, we include it in our local.conf file.
https://onedigi.atlassian.net/browse/DEL-7574
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
Because python2 is deprecated, all packages that depend on python2 were moved
from main layers to a specific meta-python2 layer.
https://jira.digi.com/browse/DEL-7508
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
The buildserver uses this default value when building framebuffer images. Since
the WebKit is not yet compatible with framebuffer images, the builds fail.
Remove dey-image-webkit from the default target lists.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
Since this component pulls in Optee dependencies, which in turn depend on
packages from meta-python2, add this layer to the ccimx8mn-dvk's default
bblayers.
Signed-off-by: Mike Engel <Mike.Engel@digi.com>
https://jira.digi.com/browse/DEL-7025
This image is very similar to dey-image-qt, but it includes the WebKit
packagegroup instead of the Qt one. Said packagegroup contains all of the
elements needed to run a WebKit-based browser environment in DEY.
This image requires the meta-webkit layer, so include it in our default
bblayers template. For now, include all WebKit related recipes in a dynamic
layer, because the ccimx6ul doesn't support WebKit and its projects don't need
meta-webkit at all.
https://jira.digi.com/browse/DEL-7339
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>
This commit fixes an intermittent issue when we are cloning several
repos with a huge history, throwing an unexpected error.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
If we want to share the downloads folder between projects
we need to move it outside to don't remove it.
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
These platforms are not supported on DEY 2.6 yet, and a project created for
either of them will fail during the build.
Signed-off-by: Gabriel Valcazar <gabriel.valcazar@digi.com>