Created attachment 4617 [details] bitbake -e example 2>&1 > bitbake_e_example.output Running the example recipe create as a result of `bitbake-layers create-layer` doesn't print to stdout even though it has `bb.plain()`. Steps to reproduce: ``` source oe-init-build-env bitbake-layers create-layer custom_layer bitbake-layers add-layer custom_layer # Make sure the lack of output is not caused because the task was cached echo 'do_build[nostamp]="1"' >> custom_layer/recipes-example/example/example_0.1.bb bitbake example ``` Additional findings: Doing the similar thing with the same bitbake directory but with the https://www.yoctoproject.org/docs/3.0/bitbake-user-manual/bitbake-user-manual.html#the-hello-world-example results in the bb.plain() to be seen in the output.
I've tested the exact same steps just with warrior. The results are the same. Also tried running the build task explicitly: bitbake example -c build but it didn't make a difference.
Taking a look at tmp/work/i586-poky-linux/example/0.1-r0/temp/ there are no do_build related files. ll tmp/work/i586-poky-linux/example/0.1-r0/temp/*do_build* returns nothing.
The problem seems to be tied only to do_build. Using do_install with the exact same code prints correctly. ``` SUMMARY = "bitbake-layers recipe" DESCRIPTION = "Recipe created by bitbake-layers" LICENSE = "MIT" python do_install() { bb.plain("***********************************************"); bb.plain("* *"); bb.plain("* Example recipe created by bitbake-layers *"); bb.plain("* *"); bb.plain("***********************************************"); } do_install[nostamp]="1" ```
I think this is because do_build is a "noexec" task and hence doesn't execute any task contents. I therefore believe its working as intended. You could make the bitbake example do the same with: do_build[noexec] = "1"