From 4a98bd02ab8918e639353829b221b0c4b6c58165 Mon Sep 17 00:00:00 2001 From: Tom Zanussi Date: Thu, 7 Mar 2013 18:39:00 -0600 Subject: perf: rename perf.inc to perf-features.inc The contents of perf.inc are really specific to perf features and shouldn't use the generic perf.inc name, which implies common recipe code. It's always confusing to open up this file and find out that's not what it is. Signed-off-by: Tom Zanussi Signed-off-by: Richard Purdie --- meta/recipes-kernel/perf/perf-features.inc | 22 ++++++++++++++++++++++ meta/recipes-kernel/perf/perf.inc | 22 ---------------------- meta/recipes-kernel/perf/perf_3.4.bb | 2 +- 3 files changed, 23 insertions(+), 23 deletions(-) create mode 100644 meta/recipes-kernel/perf/perf-features.inc delete mode 100644 meta/recipes-kernel/perf/perf.inc (limited to 'meta') diff --git a/meta/recipes-kernel/perf/perf-features.inc b/meta/recipes-kernel/perf/perf-features.inc new file mode 100644 index 0000000000..b8859ab7d5 --- /dev/null +++ b/meta/recipes-kernel/perf/perf-features.inc @@ -0,0 +1,22 @@ +PERF_FEATURES_ENABLE ?= "perf-scripting perf-tui" + +def perf_feature_enabled(feature, trueval, falseval, d): + """ + Check which perf features are enabled. + + The PERF_FEATURES_ENABLE variable lists the perf features to + enable. Override it if you want something different from what's + listed above, which is the default. If empty, the build won't + enable any features (which may be exactly what you want, just a + barebones perf without any extra baggage, what you get if you + specify an empty feature list). + + Available perf features: + perf-scripting: enable support for Perl and Python bindings + perf-tui: enable support for the perf TUI (via libnewt) + + """ + enabled_features = d.getVar("PERF_FEATURES_ENABLE", True) or "" + if feature in enabled_features: + return trueval + return falseval diff --git a/meta/recipes-kernel/perf/perf.inc b/meta/recipes-kernel/perf/perf.inc deleted file mode 100644 index b8859ab7d5..0000000000 --- a/meta/recipes-kernel/perf/perf.inc +++ /dev/null @@ -1,22 +0,0 @@ -PERF_FEATURES_ENABLE ?= "perf-scripting perf-tui" - -def perf_feature_enabled(feature, trueval, falseval, d): - """ - Check which perf features are enabled. - - The PERF_FEATURES_ENABLE variable lists the perf features to - enable. Override it if you want something different from what's - listed above, which is the default. If empty, the build won't - enable any features (which may be exactly what you want, just a - barebones perf without any extra baggage, what you get if you - specify an empty feature list). - - Available perf features: - perf-scripting: enable support for Perl and Python bindings - perf-tui: enable support for the perf TUI (via libnewt) - - """ - enabled_features = d.getVar("PERF_FEATURES_ENABLE", True) or "" - if feature in enabled_features: - return trueval - return falseval diff --git a/meta/recipes-kernel/perf/perf_3.4.bb b/meta/recipes-kernel/perf/perf_3.4.bb index 22feb462dc..3c499224c7 100644 --- a/meta/recipes-kernel/perf/perf_3.4.bb +++ b/meta/recipes-kernel/perf/perf_3.4.bb @@ -11,7 +11,7 @@ LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7" PR = "r8" -require perf.inc +require perf-features.inc BUILDPERF_libc-uclibc = "no" -- cgit v1.2.3