Super awesome! Applied, thanks :-)

Hello, I am trying to build yocto project and having following error: ========================== ERROR: Unable to start bitbake server (None) ERROR: Server log for this session

Coverts the firefly-rk3288, tinker-rk3288, and vyasa-rk3288 machines to use wic instead of the rockchip-gpt-img class. The rock2-squared machine has to keep the older image class because u-boot

then you could use an anonymous python function instead. python () { _buildtype = d.getVar('MESA_BUILD_TYPE') if _buildtype not in ['release', 'debug']:

ping again

* Update USERADD_ERROR_DYNAMIC[doc] and the first paragraph to match the definition in meta/conf/documentation.conf. * Add a note explaining the differences in behavior when setting

Signed-off-by: Peter Kjellerstedt <peter.kjellerstedt@...> --- documentation/ref-manual/migration.xml | 4 ++-- documentation/ref-manual/ref-variables.xml | 20 +++++++++----------- 2 files

lol Apparently writing long emails is therapeutic for me. I did propose a 3rd way (in the original email) which does work which is very similar to what you're suggesting: # set the build type to

Excellent, that explains a lot, thanks! So in this case, the answer to the question of "when" is: never :-)

<richard.purdie@...> wrote: right... so my array is not 2D, but 3D then! but as i just said, i missed the addtask in the first email.

hey Trevor, right.. I was confused, I missed a few things in your email (well, it was really long ;). I missed the fact that you were using a task. You can probably call do_check_build_type() when

Tasks run in isolation, if you change the datastore in a task it has no way to get "seen" by other tasks. They're separate processes. That is why the setVar in a task has no effect outside that

Ooh, I like this already! Your row/column concept is a good mental map of the process. Your explanation cleared up the "bitbake -e" vs "bitbake -e <bar>" case for me too! Whether I move the above to

Hi, I don't is alsa is your actual issue, even if the kernel seems that it's stuck there, but in any case you can remove the alsa from your distro. I guess you're using poky as base distro, so add

Excellent , thanks Joe. Peter.

[Re: [yocto] [meta-selinux] Dependency loop help with selinux userspace/python3/util-linux] On 19.12.11 (Wed 09:21) Peter Morrow via Lists.Yoctoproject.Org wrote: No, no issue as far as I can tell,

Hi everyone, So I am relatively new to the project and I have successfully been a able to make a few builds following the really well crafted documentation. I however have a few issues regarding my

well the easiest way to visualize it is to think about all variables being in a large array. Each variable (each row) having a different 'value' for each 'column' and each column representing a

wrote: Hi Yi, Great! Is there anything stopping these patches being merged? Thanks, Peter.

Is there a document, or better yet a diagram, showing the order in which various config files, recipes, tasks, etc are parsed? Figuring out the order of the config files is easy enough