From patchwork Fri Sep 14 21:09:37 2012 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: [bitbake-devel] v3 or so [PATCH 0/1] File inclusion tracking (cleaned up) Date: Fri, 14 Sep 2012 21:09:37 -0000 From: Peter Seebach X-Patchwork-Id: 36555 Message-Id: To: bitbake-devel This is *just* the file inclusion tracking. Spent a while looking at it, improved it, got some great advice from a friend who is better at Python, improved it more, and ended up with something I think is much more maintainable and much clearer. The include tracking cost is minimal (the expensive stuff went away), so it's currently done unconditionally. As before, the main implication is that bitbake -e output starts out: # # INCLUDE HISTORY: # # /home/seebs/poky/build/conf/bblayers.conf # /home/seebs/poky/meta/conf/layer.conf # /home/seebs/poky/meta-yocto/conf/layer.conf # /home/seebs/poky/meta-yocto-bsp/conf/layer.conf # conf/bitbake.conf includes: # /home/seebs/poky/meta/conf/abi_version.conf [...] The idea is that if you are getting syntax errors in a file, and you don't even know *why*, this makes it possible to see. For a smallish build, the include history is only maybe 50-60 lines, so it's not a big impact on the size of the bitbake -e output. The following changes since commit ac75b06744e73399ca1fbda322ef851ae5754b0a: Valentin Popa (1): Implement 'settings' dialog as designed are available in the git repository at: git://git.yoctoproject.org/poky-contrib seebs/include http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=seebs/include Peter Seebach (1): data_smart.py and friends: Track file inclusions for bitbake -e lib/bb/cooker.py | 5 +++++ lib/bb/data_smart.py | 44 ++++++++++++++++++++++++++++++++++++++++++++ lib/bb/parse/__init__.py | 3 ++- 3 files changed, 51 insertions(+), 1 deletions(-)