I merged 2-4 of this series, unfortunately this resulted in a few issues overnight: https://autobuilder.yoctoproject.org/typhoon/#/builders/85/builds/1393 which is due to the non-executable script

You can use both by changing the directory for downloads and sstate-cache. Put these in your local.conf: SSTATE_DIR = "/opt/sstate-cache" DL_DIR = "/opt/downloads" (You change "/opt" to some other

try adding INHERIT += "rm_work" to local.conf and see if that helps

I had proceeded the Build image process with Home directory and got stuck with low disk space. Now, the build image process is stopped almost near to last stage. Please provide me any suggestion to

Richard, I think that the web server for: https://autobuilder.yocto.io/pub/non-release/ runs every 30 seconds via cron so if you are happy with this crude dd trigger once things have soaked in

We were using it for testing on the YP AB and thought it would be useful if at some point the monitoring was dropped from the default config. I think we can just add it later if needed. ../Randy --

I had a quick look at the code and sadly, it doesn't appear I implemented  nesting so this wouldn't be that useful as things stand. Cheers, Richard

Hi I am new to Yocto project and have little experience in Linux. In my computer, Root folder is having free space of 65 GB and Home is having 45 GB free space. Shall I get the poky in root folder and

Is the template used anywhere? I can't remember if we support nesting templates in which  case this is useful, or not? Cheers, Richard

for a current project (and subsequent projects), i want to define a hardware bringup image; that is, a really basic image chock-full of low-level utilities for debugging initial board bringup. this

Hi, Could you please let me know if there is any update on this change? Thanks & Regards, Purushottam

From: Meng Li <Meng.Li@...> Signed-off-by: Meng Li <Meng.Li@...> --- conf/layer.conf | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/conf/layer.conf

Hi, My comments are inline. ... if everybody does what they are supposed to - which is not the case. This does not sound too bad. This would also mean, that if the outside repo dies you can still

I was able to solve it by forcing recompiling nodejs with `bitbake -f -c compile nodejs` Not sure what happened there -- Alessandro Tagliapietra

Hi everyone, I've installed nodejs and node-red by using meta-oe and meta-iot-cloud, with IMAGE_INSTALL_append = " nodejs node-red bash" it was initially working but then I've got some pseudo aborts

Working with zeus 3.0.4, extended SDK… Could someone explain what I overlooked, or why this issue pops up with python-native support inclusion ? Thanks… When I add in native-python3

Yocto Technical Team Minutes, Engineering Sync, for April 13, 2021 archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit == announcements == The upcoming Yocto

From: Yann Dirson <yann@...> FIXME: - provide an .scc with proper information - maybe bundle with dts overlay - select a more suitable path in config namespace ---

From: Yann Dirson <yann@...> FIXME: - this is not specific to the board, and would indeed apply to any SoC supported by OP-TEE. - should rather be selected by "optee" in

From: Yann Dirson <yann@...> This is the current state of working patches being discussed in https://github.com/OP-TEE/optee_os/issues/4542 --- conf/machine/include/rk3399.inc