linux/poky.git/bitbake/lib/bb/parse/__init__.py, branch dylanMirror of git.yoctoproject.org/pokyhttps://git.enea.com/cgit/linux/poky.git/atom?h=dylan2013-01-18T12:35:19+00:00bitbake: bitbake: data_smart.py and friends: Track file inclusions for bitbake -e2013-01-18T12:35:19+00:00Peter Seebachpeter.seebach@windriver.com2013-01-18T11:45:22+00:00urn:sha1:4dd6d9139cb77f2b0ff7ab9482e853108efad5aa
This code adds inclusion history to bitbake -e output, showing
which files were included, in what order. This doesn't completely
resolve timing questions, because it doesn't show you which lines
of a file were processed before or after a given include, but it
does let you figure out what the path was by which a particular
file ended up in your build at all.
How it works: data_smart acquires a .history member, which is an
IncludeHistory; this represents the inclusion of a file and all its
inclusions, recursively. It provides methods for including files,
for finishing inclusion (done as an __exit__), and for
dumping the whole tree.
The parser is modified to run includes inside a with() to push
and pop the include filename.
RP Modifications:
a) Split Include and Variable tracking
b) Replace deepcopy usage with dedicated copy function
c) Simplify some variable and usage
(Bitbake rev: b2dda721262da8abb7dc32d019e18fbc32ed8860)
Signed-off-by: Peter Seebach <peter.seebach@windriver.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: parse/cache/cooker: Preserve order in the file inclusion list2012-11-20T15:31:56+00:00Richard Purdierichard.purdie@linuxfoundation.org2012-11-19T15:01:20+00:00urn:sha1:5de7744a49bc0523fd65356638457bc51e1b262f
The data returned by get_file_depends() may me used in contexts like
checksums where order is important. The current usage of sets means
that some of the checksums can change in circumstances they should not.
This patch changes to use lists, thereby removing the problem.
(Bitbake rev: a44285fc4109236ab89f7aad0a1fc9220eec19b6)
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: Added BBINCLUDED variable.2012-02-28T12:27:21+00:00Lianhao Lulianhao.lu@intel.com2012-02-28T03:22:40+00:00urn:sha1:959981da53913090575e16d6d942148c24988615
Added new variable BBINCLUDED indicating the file dependency
information. It exposes the internal variable '__base_depends' and
'__depends'.
(Bitbake rev: af524a656fce32d01687481b86c31bef00eb9fc3)
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: add file and line number to ParseError2012-02-23T22:52:15+00:00Paul Eggletonpaul.eggleton@linux.intel.com2012-02-23T17:38:08+00:00urn:sha1:99d326a818a49faf457c707ceeec6163bf8c8e16
Ensure that a file and line number are reported for ParseError where
possible. This helps particularly in the case of inherit and require
which previously did not report either of these upon failure.
(Bitbake rev: f588ba69622a2df35417ced184e56c79ac1b40d5)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
bitbake: Update users of getVar/setVar to use the data store functions directly2011-11-27T10:35:30+00:00Richard Purdierichard.purdie@linuxfoundation.org2011-11-25T14:57:53+00:00urn:sha1:4cd96710785eb05abeff1f281878655118d4a7dd
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
parse: Use constants from stat instead of magic numbers2011-01-04T15:00:07+00:00Bernhard Reutner-Fischerrep.dot.nop@gmail.com2011-01-03T19:57:19+00:00urn:sha1:9ed8e9f37136ee170433effad0ebd4130dc97007
(Bitbake rev: bcabe2dfb587042e139890329ff52d9bb9201cf4)
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake: Sync a load of whitespace and other non-functionality changes with bitbake uptream2011-01-04T14:46:54+00:00Richard Purdierpurdie@linux.intel.com2011-01-01T23:55:54+00:00urn:sha1:0090a798eb868ebc926944eac2e6d4a5aff3e1b3
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
parse: use bb.utils.which2011-01-04T14:46:52+00:00Chris Larsonchris_larson@mentor.com2010-12-17T18:54:09+00:00urn:sha1:717f13d63cb904ce48533d3f1b2b00d278741f6f
(Bitbake rev: 2bc893dc407bf608cac7e12673161b75b712da83)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Switch bitbake internals to use logging directly rather than bb.msg2011-01-04T14:46:33+00:00Chris Larsonchris_larson@mentor.com2010-06-10T17:35:31+00:00urn:sha1:ecc68fa4fbb579e97ea45156e79a293b073697a0
We use a custom Logger subclass for our loggers
This logger provides:
- 'debug' method which accepts a debug level
- 'plain' method which bypasses log formatting
- 'verbose' method which is more detail than info, but less than debug
(Bitbake rev: 3b2c1fe5ca56daebb24073a9dd45723d3efd2a8d)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
bitbake/siggen: Ensure full signature data is not held unless needed, reducing memory consumption2010-09-29T09:47:17+00:00Richard Purdierpurdie@linux.intel.com2010-09-28T21:24:13+00:00urn:sha1:9747616600b424e8c0d7075a9b516a12d65a17c3
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>