The are several advantages to use the yocto recipe as base:
- The checkout of the git repo is done differently: it makes the
do_fetch task faster than it would be with the default behavior which
is to clone the entire repository.
- It is possible to share part of the build process by defining the
KMACHINE variable: All machines with the same KMACHINE value will
share (at least part of) the build environment, speeding up compile
time.
- It is possible to conditionally add configs through the
KERNEL_FEATURES variable, without needing to rebuild from scratch when
changing the features.
The new recipe also directly takes advantage of the KERNEL_FEATURES to
add support for init ram disks.
A another change happening with this commit is the kernel modules to
autoload being defined in a single file and (as the defconfig) depend on
the SOC_FAMILY variable (sitara or armada).
id:413752
instead of using the keys generated inside build/key by
coreos-init-buildenv, we use a fixed set of keys by default
so that we can share the sstate output that use thoses keys to
share binaries between the CI state server and developers local
installation.
There was an issue in the submodules of coreos and in in nwl
there were two entries for the submodule coreos in .gitmodules.
Thus one submodule entry was removed.
Signed-off-by: Marc Mattmüller <marc.mattmueller@netmodule.com>
- replace PRODUCT by NWL in nwl-init-build-env
- add meta-nwl-distro to bblayers.conf.sample
- remove the meta-belden-coreos-demo layers by default
- add some branding
Squashed commit of the following:
commit e3ece0d4f75e6f37accd731f70c0071f3643b62a
commit 3c7e0567e523c6d2951883089e4944aa32d6a150
commit 29065139af735c71478d14c2316af80309bcaa1d
Signed-off-by: Patrick Zysset <patrick.zysset@netmodule.com>