[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAK7LNAT3NQnTtdxyz79jgoQHoUS0TxkP99yuoY-N5yALLnFO1A@mail.gmail.com>
Date: Fri, 5 Oct 2018 19:48:34 +0900
From: Masahiro Yamada <yamada.masahiro@...ionext.com>
To: "Luis R. Rodriguez" <mcgrof@...nel.org>
Cc: Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
Randy Dunlap <rdunlap@...radead.org>,
Sam Ravnborg <sam@...nborg.org>, Petr Vorel <pvorel@...e.cz>,
Steven Rostedt <rostedt@...dmis.org>,
Johannes Berg <johannes@...solutions.net>,
Valentin Rothberg <valentinrothberg@...il.com>,
Vegard Nossum <vegard.nossum@...cle.com>, nbd@....name,
kconfig-sat@...glegroups.com
Subject: Re: [ANN] init-kconfig - easy way to embrace Linux's kconfig
Hi,
On Fri, Oct 5, 2018 at 5:03 AM Luis Chamberlain <mcgrof@...nel.org> wrote:
>
> Every now and then a project is born, and they decide to use Linux's
> kconfig to enable configuration of their project. As it stands we *know*
> kconfig is now used in at least over 12 different projects [0]. I myself
> added kconfig to one as well years ago. Even research reveals that
> kconfig has become one of the leading industrial variability modeling
> languages [1] [2].
>
> What is often difficult to do though is to start off using kconfig and
> integrating it into a project. Or updating / syncing to the latest
> kconfig from upstream Linux.
>
> I had yet another need to use kconfig for another small project so
> decided to make a clean template others can use and help keep it in sync.
> This is a passive fork which aims to keep in sync with the Linux
> kernel's latest kconfig to make it easier to keep up to date and to
> enable new projects to use and embrace kconfig on their own. The goal
> is *not* to fork kconfig and evolve it separately, but rather keep in
> sync with the evolution of kconfig on Linux to make it easier for
> projects to use kconfig and also update their own kconfig when needed.
Syncing kconfig files is easy
since the files are collected in the single place, scripts/kconfig/.
It is true you need some efforts to introduce Kconfig in your project,
but once established, it is just a matter of copying files
under scripts/kconfig.
Copying stuff directly from Linux would be as easy as
doing so from your init-kconfig.
> This may also be useful if folks want to test R&D code on a smaller
> compartamentalized codebase.
>
> If you find this useful and you'd like to help keep it in sync, send
> patches my way as the kernel's kconfig evolves. The code is up on
> gitlab [3].
>
> Do we want to document this option on Linux in case folks want to try
> and embrace kconfig on their own for other projects?
>
> [0] http://www.eng.uwaterloo.ca/~shshe/kconfig_semantics.pdf
> [1] http://gsd.uwaterloo.ca/sites/default/files/vm-2013-berger.pdf
> [2] http://gsd.uwaterloo.ca/sites/default/files/ase241-berger_0.pdf
> [3] https://gitlab.com/mcgrof/init-kconfig
>
> Luis
Looks like init-kconfig is trying to build some objects as demo.
obj-y = main.o
obj-$(CONFIG_FOO) += foo.o
obj-$(CONFIG_BAR) += bar.o
obj-$(CONFIG_BAZ) += baz.o
obj-$(CONFIG_ALPHA) += alpha/
FWIW, this is something I played with some time ago.
Kbuild Skeleton
https://github.com/masahir0y/kbuild_skeleton
It consists of some core Makefiles and Kconfig.
>From the time-stamp, it is already 6 years too old.
I am not sure if it is useful for people,
if so, it is pretty easy to sync up with the latest Linux.
--
Best Regards
Masahiro Yamada
Powered by blists - more mailing lists