Daniel,
as discussed, I've experimented with meta-rpb and the Yocto Compatible
check scripts.. see :
https://www.yoctoproject.org/docs/2.6/mega-manual/mega-manual.html#making-s…
There are many obvious reasons why it's a good idea to make sure that
layers can pass this script..
I was able to get meta-rpb to pass the compatibility check with the
following patches:
https://github.com/ndechesne/meta-rpb/tree/check-layer
The simplest way to run the script is to use a copy of Poky git:
$ git clone http://git.yoctoproject.org/git/poky
$ cd poky
$ source oe-init-build-env
$ yocto-check-layer <oe-rpb folder>/layers/meta-rpb/ --dependency
<oe-rpb folder>/layers/
The main things that the script will test are:
1. Adding your layer in bblayers.conf will not change any recipe
content/checksum
2. All dependencies are properly tracked
For meta-rpb, we depend on meta-virtualization (docker) and that layer
breaks compatibility in many ways.. so I had to remove references to
docker and meta-virt to run the script..
I will be doing a bit more testing/review, and submit the PR.
cheers
nico
hi,
i've started to push some updates about OE warrior for our Linaro builds.
The branch warrior was added to meta-rpb, meta-96boards, meta-qcom,
meta-linaro, meta-backports.
I have added a 'warrior' branch to the oe-rpb-manifest as well, see:
https://github.com/96boards/oe-rpb-manifest/commit/dd60a2322845adb9cfe7e82e…
Some layers still don't have a warrior branch, in which case we use master.
I have submitted a change to start build based on warrior..
Let's see how things go with this new branch!
cheers
nico
