From: Masahiro Yamada <yamada.masahiro@socionext.com>
To: linux-kbuild@vger.kernel.org
Cc: Sam Ravnborg <sam@ravnborg.org>,
Ulf Magnusson <ulfalizer@gmail.com>,
Randy Dunlap <rdunlap@infradead.org>,
Masahiro Yamada <yamada.masahiro@socionext.com>,
linux-kernel@vger.kernel.org,
Philippe Ombredanne <pombredanne@nexb.com>,
Michal Marek <michal.lkml@markovi.net>,
Kate Stewart <kstewart@linuxfoundation.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arvind Prasanna <arvindprasanna@gmail.com>
Subject: [PATCH 0/5] kconfig: refactor package checks for GUI frontends
Date: Fri, 18 May 2018 13:52:21 +0900 [thread overview]
Message-ID: <1526619146-1895-1-git-send-email-yamada.masahiro@socionext.com> (raw)
Kconfig supports 4 GUI frontends.
Each of them needs some support packages, but checks them differently:
qconf, gconf: check packages in Makefile (pkg-config is required)
mconf: lxdialog/check-lxdialog.sh
nconf: needs ncurses, but its presence is not checked
This series refactor the package checks so that all of them work
in the same way.
The package check scripts have been moved to scripts/kconfig/*conf-cfg.sh
The motivation of this clean-up is Randy's following patch:
https://patchwork.kernel.org/patch/10277723/
I want to clean up existing code before adding more checks.
Masahiro Yamada (5):
kbuild: do not display CHK for filechk
kconfig: refactor Qt package checks for building qconf
kconfig: refactor GTK+ package checks for building gconf
kconfig: refactor ncurses package checks for building mconf
kconfig: refactor ncurses package checks for building nconf
scripts/Kbuild.include | 1 -
scripts/kconfig/Makefile | 160 ++++++++++-------------------
scripts/kconfig/gconf-cfg.sh | 23 +++++
scripts/kconfig/lxdialog/check-lxdialog.sh | 93 -----------------
scripts/kconfig/lxdialog/dialog.h | 2 +-
scripts/kconfig/mconf-cfg.sh | 24 +++++
scripts/kconfig/nconf-cfg.sh | 22 ++++
scripts/kconfig/qconf-cfg.sh | 25 +++++
8 files changed, 148 insertions(+), 202 deletions(-)
create mode 100755 scripts/kconfig/gconf-cfg.sh
delete mode 100755 scripts/kconfig/lxdialog/check-lxdialog.sh
create mode 100755 scripts/kconfig/mconf-cfg.sh
create mode 100644 scripts/kconfig/nconf-cfg.sh
create mode 100755 scripts/kconfig/qconf-cfg.sh
--
2.7.4
next reply other threads:[~2018-05-18 4:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 4:52 Masahiro Yamada [this message]
2018-05-18 4:52 ` [PATCH 1/5] kbuild: do not display CHK for filechk Masahiro Yamada
2018-05-18 4:52 ` [PATCH 2/5] kconfig: refactor Qt package checks for building qconf Masahiro Yamada
2018-05-19 18:10 ` Randy Dunlap
2018-05-18 4:52 ` [PATCH 3/5] kconfig: refactor GTK+ package checks for building gconf Masahiro Yamada
2018-05-19 18:11 ` Randy Dunlap
2018-05-18 4:52 ` [PATCH 4/5] kconfig: refactor ncurses package checks for building mconf Masahiro Yamada
2018-05-19 18:02 ` Randy Dunlap
2018-05-20 8:21 ` Masahiro Yamada
2018-05-18 4:52 ` [PATCH 5/5] kconfig: refactor ncurses package checks for building nconf Masahiro Yamada
2018-05-19 18:30 ` [PATCH 0/5] kconfig: refactor package checks for GUI frontends Randy Dunlap
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=1526619146-1895-1-git-send-email-yamada.masahiro@socionext.com \
--to=yamada.masahiro@socionext.com \
--cc=arvindprasanna@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.lkml@markovi.net \
--cc=pombredanne@nexb.com \
--cc=rdunlap@infradead.org \
--cc=sam@ravnborg.org \
--cc=ulfalizer@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.