summaryrefslogtreecommitdiffstats
path: root/bitbake/lib/bb/methodpool.py
Commit message (Collapse)AuthorAgeFilesLines
* bitbake: methodpool: Retire it, remove global method scopeRichard Purdie2013-05-241-42/+0
| | | | | | | | | | | | | | | | | Having a global method scope confuses users and with the introduction of parallel parsing, its not even possible to correctly detect conflicting functions. Rather than try and fix that, its simpler to retire the global method scope and restrict functions to those locations they're defined within. This is more what users actually expect too. If we remove the global function scope, the need for methodpool is reduced to the point we may as well retire it. There is some small loss of caching of parsed functions but timing measurements so the impact to be neglibile in the overall parsing time. (Bitbake rev: 4d50690489ee8dc329a9b0c7bc4ceb29b71e95e9) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: methodpool: Conflicting methodnames should be a fatal errorRichard Purdie2013-05-241-1/+1
| | | | | | | | | | When this error occurs, the build should stop, not continue uninterrupted. [YOCTO #4460] (Bitbake rev: acd6d7ffa8813b3b11cad9145e8e614a695ae04a) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: methodpool: Clean up the parsed module list handling to be slightly ↵Richard Purdie2012-08-231-8/+9
| | | | | | | | | | | | less insane This removes some dubious functions and replaces them with a simpler, cleaner API which better describes what the code is doing. Unused code/variables are removed and comments tweaked. (Bitbake rev: f1e943aebfb84e98253f3f21646d6765c4fa1d66) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* bitbake: methodpool: Remove unused check_insert_method functionRichard Purdie2012-08-231-14/+0
| | | | | | (Bitbake rev: 4664333e55ffc9d618f2c2f074200923209fd6c4) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* methodpool: Improve method already seen error messageRichard Purdie2012-06-141-1/+1
| | | | | | | | | | | The current error message is confusing, this improves it to explain the problem and the possible ways to resolve it. [YOCTO #2530] (Bitbake rev: d316f28ed725ff40daa8771c1aa224ac46d5b224) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
* Consolidate the exec/eval bits, switch anonfunc to better_exec, etcChris Larson2010-07-021-5/+5
| | | | | | | | | | | | The methodpool, ${@} expansions, anonymous python functions, event handlers now all run with the same global context, ensuring a consistent environment for them. Added a bb.utils.better_eval function which does an eval() with the same globals as better_exec. (Bitbake rev: 424d7e267b009cc19b8503eadab782736d9597d0) Signed-off-by: Chris Larson <chris_larson@mentor.com> Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
* bitbake: Sync with upstream. Richard Purdie2007-01-081-25/+10
| | | | | | | | | | | | | * File licence headers were sanitised causing most of the diff. * cooker.py was created from bin/bitbake. * cvs fetcher port option was added * The -f force option was fixed to work correctly * Multiple entries in rrecrdeps are now handled correctly (allows adding do_deploy to image depends) git-svn-id: https://svn.o-hand.com/repos/poky/trunk@1129 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Sync with bitbake trunk for bugfixes and improved dot file ↵Richard Purdie2006-11-291-0/+1
| | | | | | generation code git-svn-id: https://svn.o-hand.com/repos/poky/trunk@987 311d38ba-8fff-0310-9ca6-ca027cbcb966
* bitbake: Upgrade from 1.4 -> 1.7.4ishRichard Purdie2006-11-161-3/+0
| | | | git-svn-id: https://svn.o-hand.com/repos/poky/trunk@863 311d38ba-8fff-0310-9ca6-ca027cbcb966
* Update to bitbake 1.4.2 (latest stable branch release). This includes the ↵Richard Purdie2006-05-091-0/+101
caching speedups git-svn-id: https://svn.o-hand.com/repos/poky/trunk@371 311d38ba-8fff-0310-9ca6-ca027cbcb966