From mboxrd@z Thu Jan 1 00:00:00 1970 From: Peter Korsgaard Date: Sun, 26 Jan 2014 21:02:52 +0100 Subject: [Buildroot] [PATCH 1/2] packages infra: add function to get a Kconfig option In-Reply-To: (Yann E. MORIN's message of "Sun, 26 Jan 2014 14:56:26 +0100") References: Message-ID: <87wqhm1pg3.fsf@dell.be.48ers.dk> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net >>>>> "Yann" == Yann E MORIN writes: > From: "Yann E. MORIN" > We so far have no mean to get the value from a Kconfig option from the > .config file of a package (eg. linux, busybox...). > Add a new function that returns the unmangled value of an option. > It expect two arguments: > - the Kconfig option name (complete, with leading CONFIG if necessary) > - the .config file to get it from > Note that, if the Kconfig option is a string, the returned value will > contain the leading and trailing double-quotes. > Signed-off-by: "Yann E. MORIN" > --- > package/pkg-utils.mk | 6 ++++++ > 1 file changed, 6 insertions(+) > diff --git a/package/pkg-utils.mk b/package/pkg-utils.mk > index 851575c..2f70acc 100644 > --- a/package/pkg-utils.mk > +++ b/package/pkg-utils.mk > @@ -52,6 +52,12 @@ define KCONFIG_DISABLE_OPT > echo "# $(1) is not set" >> $(2) > endef > +# Note: we do not indent this, since we want to avoid any leading > +# space or tabs when calling this function > +define KCONFIG_GET_OPT > +$(shell sed -e "/\\<$(1)\\>=\\(.*\\)$$/!d; s//\\1/" $(2)) Should this perhaps use $(SED)? Sorry, I'm probably missing something, but I don't right away see why we don't just use: $(SED) -n 's/^$(1)=//p' $(2) -- Bye, Peter Korsgaard