From: Luis Chamberlain <mcgrof@kernel.org>
To: Josh Triplett <josh@joshtriplett.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-kbuild@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Randy Dunlap <rdunlap@infradead.org>,
Sam Ravnborg <sam@ravnborg.org>, Petr Vorel <pvorel@suse.cz>,
Steven Rostedt <rostedt@goodmis.org>,
Johannes Berg <johannes@sipsolutions.net>,
Valentin Rothberg <valentinrothberg@gmail.com>,
Vegard Nossum <vegard.nossum@oracle.com>,
Felix Fietkau <nbd@nbd.name>,
kconfig-sat@googlegroups.com
Subject: Re: [kconfig-sat] [ANN] init-kconfig - easy way to embrace Linux's kconfig
Date: Thu, 4 Oct 2018 13:53:19 -0700 [thread overview]
Message-ID: <20181004205319.GO5238@garbanzo.do-not-panic.com> (raw)
In-Reply-To: <20181004204117.GA10640@localhost>
On Thu, Oct 04, 2018 at 01:41:18PM -0700, Josh Triplett wrote:
> I would *love* to see Kconfig in Linux evolved to be more easily reused.
This *can* happen. Let me itemize a few things off of my head I think
would need to be done as its at least fresh in my head now:
All we need from scripts/Kbuild.include is filechk and kecho (what I
have in my scripts/Kbuild.include). This could be moved to
scripts/Kbuild.basic, and so would make sync'ing easier.
The scripts/kconfig/Makefile would need a respective modifications to
make it work independently, see my scripts/kconfig/Makefile. Perhaps
the biggest pain was resolving the target for
scripts/kconfig/.mconf-cfg. If somehow we end up with a file which could
work for both environments we're set.
Other than this we'd need a simple script, say scripts/copy-kconfig.sh
which would copy over only those files I took from scripts/kconfig.
There's a few things to consider for a split copy / demo:
* versioning *is not* part of kconfig
* object building *is not* part of kconfig
But the problem I faced was that to demo kconfig I had to use *something*
for versioning and object building. The object building is simple, and
the versioning scheme was just copied from Linux.
What I ended up with the smallest demo I could come up with.
Luis
next prev parent reply other threads:[~2018-10-04 20:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 20:02 [ANN] init-kconfig - easy way to embrace Linux's kconfig Luis Chamberlain
2018-10-04 20:09 ` [kconfig-sat] " Josh Triplett
2018-10-04 20:39 ` Luis Chamberlain
2018-10-04 20:41 ` Josh Triplett
2018-10-04 20:53 ` Luis Chamberlain [this message]
2018-10-04 22:05 ` Steven Rostedt
2018-10-05 0:18 ` Randy Dunlap
2018-10-05 10:48 ` Masahiro Yamada
2018-11-21 22:58 ` [kconfig-sat] " Luis Chamberlain
2018-10-06 5:53 ` Ulf Magnusson
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=20181004205319.GO5238@garbanzo.do-not-panic.com \
--to=mcgrof@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=josh@joshtriplett.org \
--cc=kconfig-sat@googlegroups.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nbd@nbd.name \
--cc=pvorel@suse.cz \
--cc=rdunlap@infradead.org \
--cc=rostedt@goodmis.org \
--cc=sam@ravnborg.org \
--cc=valentinrothberg@gmail.com \
--cc=vegard.nossum@oracle.com \
--cc=yamada.masahiro@socionext.com \
/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