poky/scripts/lib
Paul Eggleton 10af6d86b3 devtool: rework source extraction so that dependencies are handled
Since it was first implemented, devtool's source extraction (as used by
the devtool modify, extract and upgrade subcommands) ignored other recipe
dependencies - so for example if you ran devtool modify on a recipe that
fetches from svn or is compressed using xz then it would fail if those
dependencies hadn't been built first. Now that we can execute tasks in
the normal way (i.e. tinfoil.build_targets()) then we can rework it to
use that. This is slightly tricky in that the source extraction needs to
insert some logic in between tasks; luckily we can use a helper class
that conditionally adds prefuncs to make that possible.

Some side-effects / aspects of this change worth noting:
* Operations are a little slower because we have to go through the task
  dependency graph generation and other startup processing. There's not
  really any way to avoid this though.
* devtool extract didn't used to require a workspace, now it does
  because it needs to create a temporary bbappend for the recipe. (As
  with other commands the workspace be created on the fly if it doesn't
  already exist.)
* I want any existing sysroot files and stamps to be left alone during
  extraction since we are running the tasks off to the side, and
  especially devtool extract should be able to be used without touching
  these. However, this was hampered by the automatic removal process in
  sstate.bbclass triggered by bb.event.ReachableStamps when the task
  signatures change, thus I had to introduce a way to disable this
  removal on a per-recipe basis (we still want it to function for any
  dependencies that we aren't working on). To implement this I elected
  to use a file written to tmp/sstate-control which gets deleted
  automatically after reading so that there's less chance of stale files
  affecting future sessions. I could have used a variable but this would
  have needed to be whitelisted and I'd have to have poked its value in
  using the setVariable command.

Fixes [YOCTO #11198].

(From OE-Core rev: 830dbd66992cbb9e731b48d56fddf8f220349666)

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2017-09-18 11:07:29 +01:00
..
bsp linux-yocto: add linux-yocto 4.12 bbappends 2017-08-31 23:37:10 +01:00
build_perf scripts/oe-build-perf-report: fix 'charts ready' console message 2017-04-05 23:22:13 +01:00
compatlayer yocto-compat-layer.py: make signature check code reusable 2017-07-06 14:38:14 +01:00
devtool devtool: rework source extraction so that dependencies are handled 2017-09-18 11:07:29 +01:00
recipetool devtool/standard: set a preferred provider when adding a new recipe with devtool 2017-09-13 22:07:42 +01:00
wic wic: accept '-' in bitbake variables 2017-09-18 11:07:29 +01:00
argparse_oe.py argparse_oe: Add int_positive type 2017-07-21 08:44:25 +01:00
scriptpath.py scripts: consolidate code to find bitbake path 2014-06-25 13:51:45 +01:00
scriptutils.py scriptutils: fix fetch_url() to use lowercase dummy recipe name 2017-08-31 23:30:03 +01:00