Age | Commit message (Collapse) | Author |
|
* poky-sync:
build: kill unneeded environment setup bits
parse: save python functions into the metadata
Include exported variables in task process env
runqueue: start implementing quieterrors
Overhaul environment handling
runqueue: resurrect use of file objects for pipein/pipeout
runqueue: clean up message log levels
runqueue: use correct task ID when checking validity of setscene tasks
Add support for 'noexec' tasks
runqueue: implement cache checking from metadata
runqueue: pass task hash information to tasks
runqueue: avoid unnecessary delays
Implement task signatures
data: Add emit_func and generate_dependencies
codeparser: Implement persistent cache
data_smart: track variable references
codeparser: add module for parsing shell/python
runqueue: implement scenequeue
fetch: add SRC_URI checksum
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
[BUGID# 645], modify the emit_var()
1. Added "#" to the beginning of each line if the comment contains
multiple lines.
2. Added "\" to the end of each line if the shell variable value
contains multiple lines.
(From Poky rev: 6f454c10bcdd5)
Signed-off-by: Lianhao Lu <lianhao.lu@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
|
|
Previously we emitted two newlines for export and unexport.
One newline for export and unexport is enough (and makes the scripts
look better and a tad smaller).
Signed-off-by: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Currently, anything whitelisted in the environment makes it into the worker
processes. This is undesireable and the worker environment should be as
clean as possible. This patch adapts bitbake sosme variables are loaded into
bitbake's datastore but not exported by default. Any variable can be exported
by setting its export flag.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
These functions allow generation of dependency data between functions and
variables allowing moves to be made towards generating checksums and allowing
use of the dependency information in other parts of bitbake.
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
it first
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
types.IntType -> int
types.StringType -> basestring
...
Also moves our ImmutableTypes tuple into our own namespace.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
We should add back in some proper unit testing. Doctest is rather limited,
and we haven't actually made use of it since the original implementation of
the datastore when the project started, as far as I'm aware.
Signed-off-by: Chris Larson <chris_larson@mentor.com>
|
|
Signed-off-by: Chris Larson <clarson@kergoth.com>
|
|
exported again (from Poky)
shell.py: When running a stage task in bbshell, run populate_staging, not the stage task (from Poky)
|
|
|
|
In preparation for python3.0 make sure our test cases
are working again.
|
|
the empty_environment() function to clear the environment
|
|
now only pass certain whitelisted variables into the data store. If BB_PRESERVE_ENV is set bitbake will use all variable from the environment. If BB_ENV_WHITELIST is set, that whitelist will be used instead of the internal bitbake one. Alternatively, BB_ENV_EXTRAWHITE can be used to extend the internal whitelist.
|
|
|
|
expand_cache (12% speedup)
|
|
|
|
|
|
calls into one place. Move buildSetVars() function calls. Cleanup whitespace. Make some of the core functions more generic.
|
|
|
|
- those scripts are not called by hand by bitbake users
and most of package linting tools (lintian/Debian, rpmlint/Fedora)
complain about not executable scripts.
- if someone want to run them by hand then he will be able to do it
with calling 'python SCRIPT'
|
|
BitBake trunk is now GPLv2 only, no mix of
MIT,FreeBSD License is left.
Update GPL headers to point to the correct
address of the FSF
Update the list of authors. Uli Luckas,
Seb Frankengul and Tim Amsell contributed to
the sourcecode as well
|
|
|
|
handling to emit_env.
|
|
|
|
and over again
|
|
|
|
|
|
Add another testcase regarding createCopy
and update_data
|
|
Remove my broken COW version, use mithros COW module
instead. Make it 'work' with the code
bitbake/lib/bb/data.py:
Update to use the iter protocol again and has_key
|
|
Make the Cookie Monster Dict a METACLASS? To
exploit automatically the COW features...
Small performance analysis is showing that this
is saving some time (and memory as well)
|
|
|
|
My first failed attempt to create something compatible
with a Dictionary with COW/parenting features
Use this new class for the Override Helpers
bitbake/lib/bb/data.py:
Update to the new data structure, it can't be treated
as a dict, it is not a dict.
We will use keys() (O(n)) and get
|
|
-Remove the 'Proxies' for the pkgdata Cache
-Remove the pkgdata() method as we now have
a different caching strategy
-Alter init_db to only take a parent and call
createCopy directly
bitbake/lib/bb/data_smart.py:
-Remove the DataSmartPackage class as it is not
needed
bitbake/lib/bb/cache.py:
-Call init_db with the only reasonable argument
|
|
bitbake/lib/bb/__init__.py:
bitbake/lib/bb/data_smart.py:
bitbake/lib/bb/cache.py:
bitbake/lib/bb/shell.py:
bitbake/bin/bitbake:
* Major cache refactoring. Change the cache to store only the data bitbake needs
for dependency calculations instead of all the metadata.
* Separate the cache code into its own file.
* Update the rest of the code to work with the cache changes.
* Temporarily break the shell's poke command.
|
|
-Only have one expand method in the dict
implementation.
-Apply some magic knowledge by feeding the
cookie master.
-Speed up update_data by asking the Cookie
Monster for help.
We do not iterate over each key, but the
keys we know that have the data we care
about. This gives a huge speed improvement
to parsing.
bitbake/lib/bb/data_smart.py:
-Make setVar more expensive by feeding the cookie
monster
|
|
Prepend the lib module instead of appending to
override the system installation
bitbake/lib/bb/data.py:
Same as above, prepend instead of append
|
|
Document the weird semantic of the setVarFlags. It behaves
more like an addVarFlags call. Existing variables are not
going to be removed.
|
|
-Pass the configuration to the persistent data instance
|