Chris Larson <[email protected]> writes: > Ahh, I see, that makes it clear, thanks for clarifying. I have a local > patch that turns cfgcmd into a bitbake variable, and runs ${cfgcmd} > "$@". > What do you think about that approach as an alternative?
It will work... I do not know the story behind 'cfgcmd' but I guess it was added to avoid code duplication in 'oenote "Running $cfgcmd..."'. This 'oenote' is probably useful for debugging. But for me, tracing program invocations is such an elementary instrument to analyze problems that I patched[1] 'bitbake' some time ago to enable shell monitoring globally. Without this (for me redundant) 'oenote' message, we could call ./configure directly (like in oe_runmake) without any shell or python helper variables. Enrico Footnotes: [1] http://www.ensc.de/bitbake/0003-trace.patch --> shell calls will be recorded in logfile _______________________________________________ Openembedded-devel mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
