Re: kbuild/kconfig for non-Linux projects

[Alexander Kriegisch <Alexander@Kriegisch.name>]

I am new to this list, but trying to reply to an older thread, re-using 
its title/subject. I am going to quote Arnaud's message because my 
question relates to it.

@Arnaud: I have successfully downloaded, installed and built a tarball 
from your 2.6.39 branch. So far, so good. What I am trying to do, 
though, is to refresh an older kbuild version, taken from Buildroot some 
about years ago. It works nicely and I especially like the warnings for 
cyclic references and missing direct dependencies.

There is one issue we are facing in our open source project 
(http://freetz.org), though: Our previous kconfig version used symbols 
which were identical in .config with the names in Config.in, i.e. they 
had no "CONFIG_" prefixes. Now kconfig writes .config files with those 
prefixes, so in order not to break our build system we had to add 
scripts replacing names back and forth before we start conf/mconf and 
after they terminate.

Question: Is there a straightforward way to make kconfig read/write 
symbols *without* "CONFIG_" prefixes? As I am not a C programmer, would 
you mind providing a patch if necessary?

Respectfully
-- 
Alexander Kriegisch


> using kconfig outside the linux kernel tree should be trivial,
> normally, as you said, all the Linux "branding" should have been made
> configurable. The trick might be to have the correct Makefile glue to
> let it build. If you want some of the work pre-done, I just pushed an
> old repository of mine on github. It should contains only what's
> needed to build the various part of kconfig:
>
> https://github.com/lacombar/kconfig/
>
> I did not really touch it since October 2010, so it is certainly
> missing parts (especially bug fixes). Moreover, it squashes commit to
> keep the history clean, but I tried to keep the shortlog to have an
> idea what has been going on. Last warning, I do not guarantee the tree
> integrity (ie. I love rebasing :))