rm_work.bbclass: inhibit rm_work per recipe
authorChen Qi <Qi.Chen@windriver.com>
Wed, 13 Mar 2013 07:01:33 +0000 (15:01 +0800)
committerRichard Purdie <richard.purdie@linuxfoundation.org>
Mon, 18 Mar 2013 13:18:21 +0000 (13:18 +0000)
commite887a2034fd3b9fc661499a6b5cbd39a91beb95f
tree723b1adb1424b07644583bbad67c469ee1dbf658
parent1a32fccd916d8e4278f27086e5470f49e3bdfa9c
rm_work.bbclass: inhibit rm_work per recipe

Use RM_WORK_WHITELIST to inhibit rm_work per recipe. In this way,
one can use rm_work for the most of the recipes but still keep the
work area for the recipe(s) one is working on.

As an example, the following settings in local.conf will inhibit
rm_work for icu-native, icu and busybox.
    INHERIT += "rm_work"
    RM_WORK_WHITELIST += "icu-native icu busybox"

If we comment out the RM_WORK_WHITELIST line and do a rebuild, the
working area of these recipes will be cleaned up.

[YOCTO #3675]

(From OE-Core rev: 6c930c3c06f2e698540626c87bd7f7f571df35ef)

Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Signed-off-by: Saul Wold <sgw@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
meta/classes/rm_work.bbclass