From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1] Add standalone kconfig infrastructure
Date: Wed, 20 Jun 2012 14:40:52 -0700 [thread overview]
Message-ID: <cover.1340228144.git.raj.khem@gmail.com> (raw)
Right now we have few packages which uses kconfig infra
besides the Linux kernel e.g. busybox, uclibc
at present they all include their own version of kconfig
infrastructure. This package called kconfig-frontends
has been created to help manage projects using kconfig
or wanting to use kconfig which are not kernel.
The package will keep lock step releases with upstream
kernel release.
This will tremendesouly help in deploying kconfig into
glibc/eglibc which is going to convert the eglibc options
into kconfig and eventually into glibc.
I do not have the eglibc patches quite ready yet. but
this is independent of that change.
The following changes since commit 6d761ae17ddbd3d936e7fe985b40825ad62b2418:
debian.bbclass: invoke target objdump (2012-06-18 13:20:29 +0100)
are available in the git repository at:
git://git.openembedded.org/openembedded-core-contrib kraj/kconfig-frontends
http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=kraj/kconfig-frontends
Khem Raj (1):
kconfig-frontends: New recipe
.../kconfig-frontends/kconfig-frontends_3.4.bb | 28 ++++++++++++++++++++
1 files changed, 28 insertions(+), 0 deletions(-)
create mode 100644 meta/recipes-devtools/kconfig-frontends/kconfig-frontends_3.4.bb
--
1.7.5.4
next reply other threads:[~2012-06-20 21:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-20 21:40 Khem Raj [this message]
2012-06-20 21:41 ` [PATCH 1/1] kconfig-frontends: New recipe Khem Raj
2012-06-21 0:55 ` Bruce Ashfield
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=cover.1340228144.git.raj.khem@gmail.com \
--to=raj.khem@gmail.com \
--cc=openembedded-core@lists.openembedded.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