When building del-image-minimal we are seeing the following errors:
NOTE: Running noexec task 1211 of 1214 (ID: 220, /home/alex/Projects/
meta-fsl-arm/recipes-multimedia/fsl-mm-core/fsl-mm-codeclib_2.0.3.bb,
do_package_write)
ERROR: QA Issue: gst-fsl-plugin rdepends on fsl-mm-codeclib-dev
ERROR: QA run found fatal errors. Please consider fixing them.
NOTE: Running task 853 of 1214 (ID: 221, /home/alex/Projects/
meta-fsl-arm/recipes-multimedia/fsl-mm-core/fsl-mm-codeclib_2.0.3.bb,
do_package)
NOTE: package fsl-mm-codeclib-2.0.3-r2.0digi.0: task do_package: Started
ERROR: QA Issue: fsl-mm-codeclib rdepends on fsl-mm-codeclib-dev
The error means that fsl-mm-codeclib and gst-fsl-plugin are including
libraries which should only be included on the dev version, typically
.so files.
This is only a workaround, the patch should come from those packages.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
WARNING: For recipe fsl-mm-codeclib, the following files/directories were installed but not shipped in any package:
WARNING: /usr/lib/lib_ogg_parser_arm9_elinux.3.0.1.07.00
WARNING: /usr/lib/lib_ogg_parser_arm11_elinux.3.0.1.07.00
Not sure why these aren't .so.x.y.z though.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Doing it in the layer configuration means we don't have to do it in
each recipe that requires it.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Now that all code is our own as we are not copying recipes into the
layer but overriden the ones in meta-fsl-arm, the prefix to comments
have no use.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
In this way the layer should still be able to compile the default
machines supported by meta-fsl-arm.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This is the same as the meta-fsl-arm layer and allows for more recipes
for different kernel versions to be considered.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Instead of having the whole recipe in meta-digi-arm, use the original
recipe in meta-fsl-arm and just add a bbappend file with some overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
- imx-digi-base includes imx-base and contains the overrides.
- mxs-digi-base includes mxs-base and contains the overrides.
- digi-defaults contains the overrides to fsl-default-settings,
fsl-default-providers and fsl-default-versions.
- The machine configuration files include the digi includes and also
contains the UBOOT load addresses overrides.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
We use the 11.09.01 tarball which also includes binary firmware for other
hardware like the sdma and atheros, but we don't install the firmware
we don't use.
Also, we include newer VPU binary files on this commit, from the
11.09.01_201112 tarball which are the ones we use in DEL.
This is also done this way in meta-fsl-arm.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The package was not including all the libraries being installed.
That is because $SOLIBS extens to *.so.*, which meant that the .so files
were not being packaged.
I won't report this upstream as probably the source tarball they use won't
have this problem.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The recipe is sourcing the tarball from Logroño's repoes which has a
different checksum than the same version included in meta-fsl-arm.
Go guess.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This commit separates the BSP layer from the DEL distribution layer. This
allows for customers to use the BSP layer while customizing their own
distribution, and for other Digi teams, like the gateways, to do the same.
It would also allow to use the DEL layer over other BSPs.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
For the del distro, override the busybox configuration to use the one
that was also used in DEL-5.9.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
This allows to specify del specific overrides in recipes, so that other
distros under meta-digi can also customize them in their own way.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
The original recipe is based in meta/recipes-core. We want to add a shadow
file for the del-image-minimal target.
The best way would be to add a bbappend overlay, however the original
recipe prepends the populate_packages function with a:
preinst = blahblah
This makes it impossible for a bbappended recipe to add anything to the
preinst script, which is needed to install the shadow file.
Hence the only solution is to duplicated the recipe and increase PR.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
del-image-minimal is the command line non graphical busybox based minimal
root filesystem for Digi Embedded Linux.
It uses a base task-del-core task, and defines core-ssh-dropbear as image
feature. It also will default to using shadow passwords unless
debug-tweak is selected in which case root can log in with an empty
password.
Signed-off-by: Alex Gonzalez <alex.gonzalez@digi.com>
Alex Gonzalez