diff options
author | Chris Larson <chris_larson@mentor.com> | 2010-07-22 11:27:10 -0700 |
---|---|---|
committer | Richard Purdie <rpurdie@linux.intel.com> | 2011-01-04 14:46:32 +0000 |
commit | 384c5cc8ac5dfd8132887603fc7eb54f2321664b (patch) | |
tree | 953aa2d73067b1a1f60dc8def51b27748a5fa54a /meta/recipes-gnome/gnome/gnome-common-2.28.0 | |
parent | 902b5da3f667f01d741cf702612698fc60a30f3b (diff) | |
download | openembedded-core-384c5cc8ac5dfd8132887603fc7eb54f2321664b.tar.gz openembedded-core-384c5cc8ac5dfd8132887603fc7eb54f2321664b.tar.bz2 openembedded-core-384c5cc8ac5dfd8132887603fc7eb54f2321664b.tar.xz openembedded-core-384c5cc8ac5dfd8132887603fc7eb54f2321664b.zip |
Add the ability to use runqueue schedulers from the metadata
If you create a runqueue scheduler class in a python module, available in the
usual python search path, you can now make it available to bitbake via the
BB_SCHEDULERS variable, and the user can then select it as they select any
other scheduler.
Example usage:
In a test.py I placed appropriately:
import bb.runqueue
class TestScheduler(bb.runqueue.RunQueueScheduler):
name = "myscheduler"
In local.conf, to make it available and select it:
BB_SCHEDULERS = "test.TestScheduler"
BB_SCHEDULER = "myscheduler"
(Bitbake rev: 4dd38d5cfb80f9bb72bc41a629c3320b38f7314d)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
Diffstat (limited to 'meta/recipes-gnome/gnome/gnome-common-2.28.0')
0 files changed, 0 insertions, 0 deletions