From: Sam Ravnborg <sam@ravnborg.org>
To: "J.A. Magallón" <jamagallon@able.es>
Cc: Lista Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Kernel GUI config
Date: Sun, 3 Nov 2002 00:29:56 +0100 [thread overview]
Message-ID: <20021102232956.GC16498@mars.ravnborg.org> (raw)
In-Reply-To: <20021102231435.GA2384@werewolf.able.es>
On Sun, Nov 03, 2002 at 12:14:35AM +0100, J.A. Magallón wrote:
> To reduce implementation efforts (and bug chasing), as someone said, you
> can take all the current parts toolkit-independent (parsers, etc.) from
> qconf and split them in a library.
If you look into scripts/kconfig you will find a shared library: libkconfig.so
Thats exactly what you ask for. A library containing the back-end.
The current frontends: oldconfig, menuconfig and xconfig are based on that.
Before getting into too much discussing about how to integrate a new
front-end lets see it.
Sam
next prev parent reply other threads:[~2002-11-02 23:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-02 23:14 J.A. Magallón
2002-11-02 23:19 ` J.A. Magallón
2002-11-02 23:27 ` Roman Zippel
2002-11-02 23:29 ` Sam Ravnborg [this message]
2002-11-03 3:32 ` Christoph Hellwig
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=20021102232956.GC16498@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=jamagallon@able.es \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®