Add standalone kconfig infrastructure
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 patch 1 replyIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/1 | kconfig-frontends: New recipemeta/ | +28 | 1 reply |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 0/1] Add standalone kconfig infrastructure
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
Signature · 1 line
1.7.5.4