'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>
Remove the current DEY variants support and framework for CC6 because in
following commits we will add support for all *hardware* variants in
just one set of DEY images for CC6.
https://jira.digi.com/browse/DEL-1569
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Remove 'dey-test' image feature and create a SARES bbclass with the
same functionality. This makes easier the creation of images suitable
for SARES testing just adding:
INHERIT += "sares-image"
to your project's local.conf
https://jira.digi.com/browse/DEL-1558
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This script + jenkins jobs allows to detect regressions on already
released versions of DEY.
https://jira.digi.com/browse/DEL-1005
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit b831229c7ac4ce9b4012ff92f50c22dcc8df7675)
This completes the support for ccimx6sbc variants:
* support device tree variants
* split variants '0x01,0x02,0x04' group in two different groups (with or
without kinetis)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 3f20015411f4e270b2e2c8faf292678c75ff2aff)
Depending on DY_BUILD_VARIANTS variable (set by Jenkins):
'false': don't build variants (only the default)
<empty>: build all the variants supported by the platform
'var1 var2': build the ones specified in the variable
https://jira.digi.com/browse/DEL-1360
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit de58d3fac52448ee7b1828c6ac71c6c10a3442ff)
https://jira.digi.com/browse/DEL-1359
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
(cherry picked from commit 015d029255eb407cca4c986562a304aef7de3940)
Added 'meta-python' to bblayers.conf.sample as it's now a dependence of
'networking-layer'. Otherwise if fails with:
ERROR: Layer 'networking-layer' depends on layer 'meta-python', but this
layer is not enabled in your configuration
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Some minor enhancements to mkproject script:
* Add 'conf-notes' files with DEY specific information. This is shown
when you create the project or when you reload the environment in an
already created project.
* Create a 'dey-setup-environment' script in the project's folder that
allows to reload the environment in a new terminal.
* Remove the PATH variable tweaking. This was needed in older versions
of Yocto, where the PATH kept growing each time you reloaded the
environment, but it has been fixed in poky, so there is no need to do
the same in our mkproject script.
https://jira.digi.com/browse/DEL-1150
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
These are key packages that we may need to debug in the buildserver, so
do not remove the object files.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Adapt the jenkins build script to build for ccardimx28js by default
linux 3.10 and u-boot 2013.01 and as alternative configuration linux
2.6.35.14 and u-boot 2009.08
https://jira.digi.com/browse/DEL-1168
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to blacklist platforms not officially supported in a DEY
release. It only works at help-level, you can actually create projects
for any platform whose config files exist, but the help of the mkproject
command will only show the officially supported platforms.
At the moment the BLACKLIST variable is not filled. This will be done in
the release branch.
https://jira.digi.com/browse/DEL-1073
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Packagegroups define sets of packages to be installed in the rootfs
*depending* on the hardware variant (~MACHINE_FEATURES). For example
installing or not the bluetooth firmware depending on machine variant
having bluetooth.
It may happen that we build sequentially machines with different
features using the same sstate and thus it may happen we end with a
rootfs lacking bluetooth firmware for a bluetooth variant.
So add all packagegroups to the list of packages to purge state-cache
between platform builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
RPM is more polished than IPK and it's the default used by
Poky/Openembedded so just use it.
https://jira.digi.com/browse/DEL-1053
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This is needed so jenkins jobs not using 'meta-digi-dey' (the layer
containing the cleaned recipe) can complete. Otherwise they fail with:
ERROR: Nothing PROVIDES 'packagegroup-dey-examples'
(for example using just the BSP layer 'meta-digi-arm' with standard
image recipes, e.g. core-image-minimal)
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
In the buildserver we share the state-cache for all the different
platforms we build in a jenkins job. This may cause problems with
some packages that have different runtime dependencies depending on
the platform or variant.
Purge then the state-cache of those problematic packages between
platform builds.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This cleans following warning:
Use of PRINC is deprecated.
The PR server should be used to automatically increment the PR.
See: https://wiki.yoctoproject.org/wiki/PR_Service
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
With the update to Dora, the BB_NUMBER_THREADS and PARALLEL_MAKE entries
in the template config file changed slightly (added a '?'), but enough
so our mkproject script failed to match and configure them properly at
project creation time.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
For daily builds just copy the firmware images to avoid running out of
space in the buildserver.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Also change the default ccardimx28js variant to 'web1' (wireless, second
ethernet, bluetooth and 1-wire)
https://jira.digi.com/browse/DEL-819
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This allows to build 'core-image-minimal' or 'core-image-sato' standard
images using only the BSP layer meta-digi-arm.
https://jira.digi.com/browse/DEL-547
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This will allow to remove the packages working directories to save disk
space.
https://jira.digi.com/browse/DEL-521
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The final product will be called "Digi Embedded for Yocto" or DEY for
short.
This commit renames all relevant files.
https://jira.digi.com/browse/DEL-474
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
If TEMPLATECONF is set in the environment, we will add the platform to
the path so that it's possible to use specific template configurations
for different platforms in the build server.
https://jira.digi.com/browse/DEL-497
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This allows to build for all supported distributions:
del (del-image-minimal)
del-gui (del-image-graphical
poky (core-image-minimal etc.)
dbl (dbl-image-base)
https://jira.digi.com/browse/DEL-481
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This will allow to pass a TEMPLATECONF path with a predefined
local.conf.template and bblayers.conf.template that will allow
to customize those files.
https://jira.digi.com/browse/DEL-468
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This will allow to compile del-image-graphical or any of the other standard
Yocto image targets as meta-toolchain, meta-toolchain-sdk, adt-installer,
or meta-ide-support.
https://jira.digi.com/browse/DEL-476
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This allows to set MACHINE_VARIANT to the empty string:
MACHINE_VARIANT = ""
in the project's local.conf by running something like:
. /path/to/mkproject.sh -v "" -p <platform>
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This script is *sourced*, so we need to make sure that the variables
used do not collide with other variables that may be already in the
environment.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
This commit adds basic support for platform variants. The script does
not make any sanity check on the variant name. It's user's
responsibility to use the correct variant for the platform.
https://jira.digi.com/browse/DEL-435
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
The script in the root directory needs to be in sync with the 'master'
script in the 'meta-digi' layer.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Some examples need hardware to be plugged to the module (e.g. the
camera), and fail if the hardware is not there.
Signed-off-by: Javier Viguera <javier.viguera@digi.com>
Javier Viguera
Urko Nalda
Alex Gonzalez
Francis Sreeves