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>
The file 'manufacturing.xml' file in the manifests repository does not exist.
When building manufacturing artifacts, we must use the 'manufacturing/morty'
branch, that already contains the right repositories to clone.
For a manufacturing job, this commit only adds the 'meta-digi-mfg' if it is not
already there.
Signed-off-by: Tatiana Leon <tatiana.leon@digi.com>
(cherry picked from commit 379ca469dff949e09c667d1a448012881b8812d2)
Signed-off-by: Gonzalo Ruiz <Gonzalo.Ruiz@digi.com>
Commit d981f999f0 introduced a new
platform with dashes on its name, which broke Jenkins build because
middle variables are being created using the name of the platform
and dashes are not allowed in bash variable names.
To fix it, this commit changes the dashes to underscores on the fly.
This is ported from a2092450fa.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Commit d981f999f0 introduced a new
platform with dashes on its name, which broke Jenkins build because
middle variables are being created using the name of the platform
and dashes are not allowed in bash variable names.
To fix it, this commit changes the dashes to underscores on the fly.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
Add initial support for Digi ConnectCore 8X SBC Express.
- ccimx6qp was used as reference machine from meta-digi.
- imx8qxpmek was used as a reference machine from meta-fsl-bsp-release.
Signed-off-by: Hector Palacios <hector.palacios@digi.com>
https://jira.digi.com/browse/DEL-5936
Add initial support for Digi's ConnectCore 6 QuadPlus SBC.
The ccimx6qp platform has the QCA6564 chip instead of the
other Atheros chips and included the Atmel ECC508A cryptographic
chip.
https://jira.digi.com/browse/DEL-5082
Signed-off-by: Arturo Buzarra <arturo.buzarra@digi.com>
As the platform data is only separated by spaces, the data is assigned
to the incorrect variable:
ccardimx28js variants: -
ccardimx28js targets: e w wb web web1 dey-image-qt
After this commit:
ccardimx28js variants: - e w wb web web1
ccardimx28js targets: dey-image-qt
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This will allow to create user helper scripts that are available (in the
PATH) when building DEY projects.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
meta-fsl-arm is no longer used for Morty release. Now the community
support is implemented in 'meta-freescale' layer.
https://jira.digi.com/browse/DEL-3451
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is the manufacturing test harness used for the CC6UL module during
manufacturing RF test.
Signed-off-by: Sebastian Pastor <sebastian.pastor@digi.com>
Instead of having one default image target for all platforms allow to
define this per platform.
This is needed because for example for the 'ccimx6ulstarter' we want to
define a default command line image instead of a QT-based one.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
We have seen lately random build failures in the buildserver due to
missing QT5 base libraries that are needed when building some other
QT5 packages.
Examples:
Compiling qtdeclarative:
error: cannot open .../tmp/work/cortexa9hf-vfp-neon-mx6qdl-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib/libQt5Core.so: No such file or directory
error: cannot open .../tmp/work/cortexa9hf-vfp-neon-mx6qdl-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib/libQt5Network.so: No such file or directory
error: cannot open .../tmp/work/cortexa9hf-vfp-neon-mx6qdl-dey-linux-gnueabi/qtbase/5.5.1+gitAUTOINC+5afc431323-r0/build/lib/libQt5Widgets.so: No such file or directory
The problem here is that 'qtdeclarative' is trying to get the needed
libraries from the 'qtbase' temporary work directory. But because in the
buildserver we have 'rm_work' enabled to save space, sometimes the
rm-work class has removed the 'qtbase' work directory before
'qtdeclarative' has been built, leading to the compilation error.
This is probably a bug in 'meta-qt5', because the different packages
needing QT5 base libraries should take them at compile time from the
sysroot and not from the qtbase work directory.
At the moment just workaround this adding an exception to the rm-work
class to not remove the 'qtbase' temporary work directory.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Gabriel Valcazar
Mike Engel
Arturo Buzarra
Tatiana Leon
Hector Palacios
Jose Diaz de Grenu
Javier Viguera
Alex Gonzalez
Sebastian Pastor
Isaac Hermida