I fixed it now (so that it compiles). The PicoTCP components didn't appear to be connected to the VM at all so I temporarily removed the VM from the CAmkES spec as it was polluting the serial output. Do you have a tardec platform to run the app on?

We do have CI but not for that particular config. We generally make sure that the CI for the seL4test/seL4bench/sel4-tutorials/camkes projects is always passing and will block broken changes from being pushed out to github until they are passing. But for less frequently used projects if upstream library changes cause them to stop building, the upstream changes will still get pushed out and therefore break the Github versions. Some projects have repo manifests that are tied to fixed released version numbers, but most just point to the tip of all of the repositories. Sometimes stuff will break. (Note: in this case with picotcp, I don't think that that configuration ever worked after being merged and it wasn't in regression). We currently don't have much CI running for the Tegra platform, at the moment we only check that the configurations compile.

From: Devel <devel-bounces@sel4.systems> on behalf of Michal Podhradsky <mpodhradsky@galois.com>
Sent: Friday, August 4, 2017 11:45 AM
To: devel@sel4.systems
Subject: [seL4] camkes-vm cma34cr_picotcp doesn't build

Hello,

when I do a fresh init of the camkes-vm repository:

repo init -u https://github.com/seL4/camkes-vm-manifest

repo sync

and then I want to build the cma34cr_picotcp app:

make clean

make make cma34cr_picotcp_defconfig

make silentoldconfig

make

I get the following error:

Makefile:76: *** No CAmkES application selected. Stop.

Do you guys have any CI server set up? If not, I would be happy to help set something up, this is not the first time an existing configuration doesn't build.

Regards

Michal