It is disabled in 5.x builds by default as it breaks the build e.g. http://git.yoctoproject.org/cgit/cgit.cgi/meta-mono/tree/recipes-mono/mono/mono-5.4.0.201.inc It's probably time to look at a

Hi all, I'm trying to build for a raspberry pi3. I need to enable two drivers for sound devices: SND_SOC_MAX9768 & MAX1363. I've created my own image recipe and that is building. Now I need to add a

Yah, not a great idea to modify the base class. It may be working, but if you actually add a patch to the SRC_URI, it will fail, since the rest of the code also needs a git repository (to apply

This patch looks good to me, merged & pushed to ptest-runner2 repo. Thanks, Joshua

I changed the code in arm/layers/core/meta/classes/kernel-yocto.bbclass From: . else                 # case: we have no git repository at all.                 # To

I am trying to compile a kernel located in SVN. I get this error message: ERROR: linux-xlnx-4.9-xilinx-v2017.2+git20-r0 do_kernel_checkout: S /tmp/stride/work-shared/plnx_arm/kernel-source is not

Thanks Alex, that has indeed resolved the problem of DEP_IMG not changing. Still getting the "trying to install files into a shared area when those files already exist" error on the second [-dvl]

Not sure if this will help, but start by not using the -dev suffix. It will clash with -dev packages produced by (any) recipe. Alex

Very little! One is: DESCRIPTION = "Das U-Boot for W2 [for development]" DEP_IMG = "u-boot-dev" PROVIDES = "u-boot-w2-dev" require u-boot-w2_1.inc The other is: DESCRIPTION = "Das U-Boot for

Hello, As we build different images for the same machine, I would like to customize the SDKPATH to include the image name. This way our application developers can install the different sdk related to

Can you share exactly how the two recipes differ? It seems that you do need to have two different build directories that differ in what MACHINE is set to. And that would configure u-boot

Following on from this, I'm trying to be able to build my two versions of u-boot, in the *same* build directory. I'm not sure if this is possible, but I figured it might be: since u-boot doesn't get

yeah that probably is a case of bundling which is on rise at app level these days, interesting, do they support any other TLS implementations ?

Hi all, Pushed a PR to github too: https://github.com/agherzan/meta-raspberrypi/pull/149 in which I fixed the two typos in this series: "firmware.in" and "zzImage". Andrei

Signed-off-by: Andrei Gherzan <andrei@...> --- recipes-bsp/common/firmware.inc | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) diff --git a/recipes-bsp/common/firmware.inc

We used to have this as the default but there was a bug at some point in the firmware which didn't work with compressed kernel images. We switched to Image and never changed it back even though that

Signed-off-by: Andrei Gherzan <andrei@...> --- recipes-devtools/pi-blaster/pi-blaster.inc | 21 --------------------- recipes-devtools/pi-blaster/pi-blaster_git.bb | 22

Signed-off-by: Andrei Gherzan <andrei@...> --- recipes-kernel/linux/linux-raspberrypi_4.9.bb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

This used to work in the past because this machine was based on raspberrypi one. Now that they are separate, we need a configuration for it too otherwise: | common/arm/quant-a.S: Assembler

Using the cmake bbclass doesn't work as it is not really a CMake project. Mono requires cmake to build the bundled BoringSSL library. I didn't look why it works in detail but I currently assume that