The instructions in README-Guide.md are a good starting point, but there are some additional guidelines in this patch for setting up worker nodes which may be useful to others who want to run their

Sending a v2 - adding an extra line or two about starting the worker(s).

The instructions in README-Guide.md are a good starting point, but there are some additional guidelines in this patch for setting up worker nodes which may be useful to others who want to run their

You're right, I don't need the others. Fixing this for the next revision. The beginning of README-Guide.md mentions that the user should reference the Yocto Manual for the required

over the years, i've always been uncomfortable with the admittedly small number of examples in various layers i've found that append to FILESEXTRAPATHS rather than prepend, so i'm curious if there is

EXT SDK, aarch64, zeus… How do I best modify the EXT SDK build env so as to reference the “vivado” env dependencies ? Is there a way to build in support so that the “module load”

Hi, I am building WiFi wlan Linux image on Zeus using Linux WiFi linux-firmware-sd8801 and connman, I need to add WiFi P2P support, is it sufficient to create wpa-supplicant_2.9.bbappend to

All, YP M+ or high bugs which moved to a new milestone in WW14 are listed below: Priority Bug ID Short Description Changer Owner Was Became Medium+ 13008 toaster

All, The below were the owners of enhancements or bugs closed during the last

All, Below is the list as of top 38 bug owners as of the end of WW14 of who have open medium or higher bugs and enhancements against YP 3.3. There are 18 possible work days left until the final

All, Just a reminder we will hold the monthly Yocto Project Technical Meeting at 8am PST tomorrow. (4/6) Yocto Project Technical Team Meeting: We encourage people attending the meeting to

All, The triage team is starting to try and collect up and classify bugs which a newcomer to the project would be able to work on in a way which means people can find them. They're being listed on

On the AB at typhoon.yocto.io only LANG=en_US.UTF-8 is set. I don't know why LC_ALL or LANGUAGE need to be set on your cluster for builds to succeed. Should we link to

Signed-off-by: Trevor Gamblin <trevor.gamblin@...> --- README-Guide.md | 94 +++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 94 insertions(+) diff --git a/README-Guide.md

upstream vendors provided me with a git repo of ALL necessary layers with the understanding that I'd clone the repo locally and disable network access, using only our local cloned repo in

Hi Yann, I've added this one to master, thanks! I'm still playing around with the others, thanks for your patience :-)

Hi Can you try this patch ( if you are using master ) and see if that helps diff --git a/recipes-devtools/clang/clang_git.bb b/recipes-devtools/clang/clang_git.bb index b8986be..b0c81f1 100644 ---

I have posted the top level CMakeList.txt in the first post, which added a sub directory INCLUDE_DIRECTORIES(include) # Add the sources to the target add_subdirectory(src) that has one

Hello, I need Clang compiler apart from currently available default gcc compiler as I am trying to compile eBPF which will run on my custom yocto which is based on core-image-minimal. Therefore I

just noticed this is meta-virt layer, file layer.conf: # The dynamic-layers directory hosts extensions and layer-specific # modifications. # # The .bbappend and .bb files are included if the