kconfig-frontendswhen either 3.7-rc6 (or final) is out.
CIRCLEQ! It's gonna be pushed soon to Linus, soit's gona be in 3.7. Hurray! Thanks to all involved in solving this issue!
CIRCLEQare needed in the parser, so even if only mconf uses them, the parser does not even build, which completely breaks the build on Cygwin. The proposed fix (using
CIRCLEQ) looks like it's not the solution, because some other old systems do not even have (complete) TAILQ, see this thread on
linux-kbuild. No proper fix in sight (although, to fix building on Cygwin, we could keep my proposed patch for
kconfig-frontendsonly, but I'm not too fond of that).
mconffrontend on Cygwin, and possibly on *BSD systems, because those systems are missing the
CIRCLEQmacros. Hopefully, that will be fixed before 3.7 is out. See also this thread and a proposed fixed on the
nconffrontend); see docs/known-issues.txt
The configuration language used by the Linux kernel, known as kconfig, has gained some traction in the community, due to its advantages:
The kconfig language is increasingly used by third-party projects, to name a few of those I know of:
Up until now, when any such project wanted to use the kconfig language as their own configuration infrastructure, the usage was to copy-paste the code from any random Linux kernel snapshot (preferrably a dot-0 release) into the project's sources, and adapt the build system inherited from the Linux kernel to the project's own build system.
Although this has more-or-less been working so far, this has a few drawbacks:
This project aims at centralising the effort of keeping an up-to-date, out of the Linux source tree, packaging of the kconfig infrastructure, ready for use by third party projects.
This package provides the kconfig parser, as well as all the frontends (all five of them, as of 2012-03-19), packaged using the traditional autotools, so the kconfig infrastructure is easy to deploy, either locally or system-wide.
kconfig-frontends package does not aim at replacing the in-tree kconfig of the linux kernel (at least in the foreseeable future!). Any fix or feature must still be pushed upstream to the Linux tree before it appears in this package.
The version numbering of
kconfig-frontends follows the linux version number, followed by
kconfig-frontends' own version digit. For example:
|Linux kernel version|| kconfig-frontends|
|3.7 (aka 3.7.0)||0||184.108.40.206|
Before the 220.127.116.11 release, the version string scheme was a bit different, and used a dash "
-" between the third and fourth digit. This has been abandoned in favor of a dot "
." so as not to confuse distributions, should they decide to package
kconfig-frontends. This old scheme was valid up to, and including the 3.6.0-0 release.
There is currently no mailing list dedicated to the
If you have an issue with the packaging itself, just drop me a note.