Currently, cooker prints the command line for sourcing oe-init-build-env when an error occurs for debugging. Sometimes it is useful to source oe-init-build-env for development reasons to access bitbake directly or some of the other tools (e.g. devtool, recipetool, oe-pkgdata-util). It would be nice if cooker could generate pre-configured scripts or have an option to source oe-init-build-env each build target.
Currently,
cooker
prints the command line for sourcingoe-init-build-env
when an error occurs for debugging. Sometimes it is useful to sourceoe-init-build-env
for development reasons to accessbitbake
directly or some of the other tools (e.g.devtool
,recipetool
,oe-pkgdata-util
). It would be nice ifcooker
could generate pre-configured scripts or have an option to sourceoe-init-build-env
each build target.