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>
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>
The build script was filtering out toolchain builds for all image
recipes not starting with 'dey-image-', but for the CC6UL we are
building by default 'core-image-base', so update the regular expression
to allow building the toolchain for 'core-image-*' image recipes.
https://jira.digi.com/browse/DEL-2837
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
- Added a checker with the job name to declare the manufacturing var
- Changed the name of the repo manifest file for the manufacturing job
- Added a checker to updated the bblayers.conf file with the mfg layer
Signed-off-by: Diego Escalona <diego.escalona@digi.com>
Using native libsdl from the system is showing problems in newer
versions of some operating systems (e.g. ubuntu 15.10). The default in
Yocto 2.0 has changed to build a native libsdl and use it instead of the
one in the system.
This commit synchronizes the config templates to the latest in Yocto
2.0.
https://jira.digi.com/browse/DEL-2586
Signed-off-by: Javier Viguera <javier.viguera@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>
Adding sdk support by copying the files from ccimx6sbc and replacing the
machine.
https://jira.digi.com/browse/DEL-2529
Signed-off-by: Isaac Hermida <isaac.hermida@digi.com>
'build-linux.digi.com' is the old DEL buildserver that sooner than later
will be decommisioned (hopefully) so just don't depend on it for DEY
builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This disables images prelink, which according to the mailing lists it's
broken for ARM and other architectures. It's also reported to make gdb
fail sometimes.
https://jira.digi.com/browse/DEL-2150
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In order to build tiny or tiny-initramfs images, the script adds
the line:
DISTRO_FEATURES_remove = "x11"
to 'conf/local.conf' file.
https://jira.digi.com/browse/DEL-2106
Signed-off-by: Urko Nalda <Urko.Nalda@digi.com>
This is needed when you use a PREMIRROR (as we usually do in buildserver
builds). Otherwise there is a strange corner case where the do_fetch
task fails when the upstream git repo has been rebased and the old mirror
tarball does not have the new SHA1 revision.
ERROR: Function failed: Fetcher failure for URL: 'git://git.yoctoproject.org/matchbox-window-manager'. Unable to fetch URL from any source.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
ccimx51js and ccimx53js are not supported in this version of DEY.
Support for those platforms is in previous versions of DEY.
https://jira.digi.com/browse/DEL-1890
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
There is only one kernel supported for each platform, so there is no
need to explicitly set the kernel preferred version.
Also:
* Remove IS_KERNEL_2X variable which is no longer needed.
* Simplify jenkins build script, now that we do not need to build two
kernel versions for ccardimx28.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The notice summarizes the different license agreements the user needs to
accept to use the software.
https://jira.digi.com/browse/DEL-1734
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 92740c610e35aa4f11ab6e6536cddb832331d896)
https://jira.digi.com/browse/DEL-1734
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 35a78b13f72963205dc1ae1e05ee851ca6cc4f28)
This was used just for SARES testing and according to the SA team it is
not needed anymore, so just remove it.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Arturo Buzarra
Tatiana Leon
Mike Engel
Isaac Hermida
Gabriel Valcazar
Francisco Gil
Hector Palacios
Jose Diaz de Grenu
Alex Gonzalez
Sebastian Pastor
Diego Escalona
Urko Nalda