public inbox for linux-kbuild@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnaud Lacombe <lacombar@gmail.com>
To: Sam Ravnborg <sam@ravnborg.org>, Roman Zippel <zippel@linux-m68k.org>
Cc: linux-kbuild <linux-kbuild@vger.kernel.org>,
	Arnaud Lacombe <lacombar@gmail.com>
Subject: [RFC 0/2] Factor Kconfig's prefix and package name
Date: Mon, 16 Aug 2010 00:54:15 -0400	[thread overview]
Message-ID: <1281934457-4225-1-git-send-email-lacombar@gmail.com> (raw)

Hi,

Many projects are using Kconfig's derivate as their configuration UI.  Some of
these projects change the default "CONFIG_" prefix for something else. It
obliges them to dig in the sources to find and replace all occurences and
associated constant. Same goes for package name where when the project ship a C
library, messages about a kernel may not be welcome. OOTH, a project may want to
limit its changes to be able to re-sync with the kernel's Kconfig and benefits
from latest features and bug fixes.

The two next patches factorizes Kconfig's prefix and package name to generic
macros defined in `scripts/kconfig/lkc.h'. This allow projects to easily tune
Kconfig for their need with trivial source modification.

There may have been similar patches in the past, in which case this message can
be silently discarded :)

any comments appreciated !

 - Arnaud

Arnaud Lacombe (2):
  kbuild: genericizes package name
  kbuild: genericizes kbuild's config prefix

 scripts/kconfig/conf.c              |   12 ++++----
 scripts/kconfig/confdata.c          |   48 +++++++++++++++++-----------------
 scripts/kconfig/gconf.c             |    4 +-
 scripts/kconfig/lkc.h               |    7 ++++-
 scripts/kconfig/mconf.c             |   44 ++++++++++++++++----------------
 scripts/kconfig/menu.c              |    2 +-
 scripts/kconfig/nconf.c             |   40 ++++++++++++++---------------
 scripts/kconfig/qconf.cc            |    6 ++--
 scripts/kconfig/zconf.tab.c_shipped |    2 +-
 scripts/kconfig/zconf.y             |    2 +-
 10 files changed, 85 insertions(+), 82 deletions(-)

-- 
1.7.2.30.gc37d7.dirty


             reply	other threads:[~2010-08-16  4:59 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16  4:54 Arnaud Lacombe [this message]
2010-08-16  4:54 ` [RFC 1/2] kbuild: genericizes package name Arnaud Lacombe
2010-08-16 11:57   ` Michal Marek
2010-08-16 12:23     ` Michal Marek
2010-08-16 17:26       ` Sam Ravnborg
2010-08-16 20:05         ` Michal Marek
2010-08-16  4:54 ` [RFC 2/2] kbuild: genericizes kbuild's config prefix Arnaud Lacombe
2010-08-16 12:36 ` [RFC 0/2] Factor Kconfig's prefix and package name Sam Ravnborg
2010-08-16 21:42   ` Arnaud Lacombe
2010-08-16 21:50     ` Sam Ravnborg
2010-08-17  1:12   ` Arnaud Lacombe
2010-08-17  2:19     ` Sam Ravnborg
2010-08-17  2:56       ` Arnaud Lacombe
2010-08-17  5:42         ` [PATCH] kbuild: implement the `mainmenu' directive Arnaud Lacombe
2010-08-17  5:44           ` [PATCH] kbuild: delay rootmenu prompt initialization Arnaud Lacombe
2010-08-17  5:52           ` [PATCH] kbuild: implement the `mainmenu' directive Arnaud Lacombe
2010-08-17 11:24           ` Michal Marek
2010-08-17 20:26             ` Sam Ravnborg
2010-08-18  2:28               ` Arnaud Lacombe
2010-08-17 20:34           ` Sam Ravnborg
2010-08-17 20:44             ` Arnaud Lacombe
2010-08-17 20:51               ` Sam Ravnborg
2010-08-17  6:15   ` [RFC 0/2] Factor Kconfig's prefix and package name Arnaud Lacombe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1281934457-4225-1-git-send-email-lacombar@gmail.com \
    --to=lacombar@gmail.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=sam@ravnborg.org \
    --cc=zippel@linux-m68k.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox