diff options
author | Paul Eggleton <paul.eggleton@linux.intel.com> | 2016-12-13 20:09:41 +1300 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2016-12-14 09:56:36 +0000 |
commit | eb63b5339014fc72ba4829714e0a96a98e135ee2 (patch) | |
tree | b757f53909d0001bd90146be647ea1f22020fc0c /meta/lib/oe | |
parent | a61d7bf8447b2d2c65eb34315c86086ff35c8bc9 (diff) | |
download | openembedded-core-eb63b5339014fc72ba4829714e0a96a98e135ee2.tar.gz openembedded-core-eb63b5339014fc72ba4829714e0a96a98e135ee2.tar.bz2 openembedded-core-eb63b5339014fc72ba4829714e0a96a98e135ee2.zip |
devtool: fix extraction of source to work in memres mode
Extracting the source for a recipe (as used by devtool's extract, modify
and upgrade subcommands) requires us to run do_fetch, do_unpack,
do_patch and any tasks that the recipe has inserted inbetween, and do so
with a modified datastore primarily so that we can redirect WORKDIR and
STAMPS_DIR in order to have the files written out to a place of our
choosing and avoid stamping the tasks as having executed in a real build
context respectively. However, this all gets much more difficult when in
memres mode since we can't call internal functions such as
bb.build.exec_func() directly - instead we need to execute the tasks on
the server. To do this we use the buildFile command which already exists
for the purpose of supporting bitbake -b, and setVariable commands to
set up the appropriate datastore.
(I did look at passing the modified datastore to the buildFile command
instead of using setVar() on the main datastore, however its use of
databuilder makes that very difficult, and we'd also need a different
method of getting the changes in the datastore over to the worker as
well.)
Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Ross Burton <ross.burton@intel.com>
Diffstat (limited to 'meta/lib/oe')
0 files changed, 0 insertions, 0 deletions