From: Michal Marek <mmarek@suse.cz>
To: Thomas De Schampheleire <patrickdepinguin+kbuild@gmail.com>
Cc: linux-kbuild@vger.kernel.org, Arnaud Lacombe <lacombar@gmail.com>
Subject: Re: kbuild/kconfig for non-Linux projects
Date: Wed, 16 Feb 2011 14:46:53 +0100 [thread overview]
Message-ID: <4D5BD54D.7070209@suse.cz> (raw)
In-Reply-To: <AANLkTimpG+9nvad8WnjaORcyZR8Yu5AaYwbQDGOWDjYJ@mail.gmail.com>
On 16.2.2011 10:08, Thomas De Schampheleire wrote:
> Hi,
>
> I'm interested in using kbuild/kconfig for other projects than the
> Linux kernel. I notice that a lot of projects (e.g. Buildroot,
> Busybox, uClibc, OpenBricks, ...) are already using this framework,
> but it's unclear to me which steps are needed to do so.
You should talk to Arnaud Lacombe, who has done quite some work in this
direction on kconfig (portability and ability to easily "rebrand"
kconfig). Honestly, I don't know if kbuild is used outside of the kernel
and if it would make sense at all. It might be easier to write the
Makefiles yourself. It's not that large and most of it is linux-specific
anyway:
$ wc -l Makefile scripts/Makefile.* scripts/Kbuild.include
1533 Makefile
405 scripts/Makefile.build
104 scripts/Makefile.clean
72 scripts/Makefile.fwinst
103 scripts/Makefile.headersinst
3 scripts/Makefile.help
170 scripts/Makefile.host
244 scripts/Makefile.lib
60 scripts/Makefile.modbuiltin
35 scripts/Makefile.modinst
153 scripts/Makefile.modpost
262 scripts/Kbuild.include
3144 total
> I found a related thread on this mailing list that seemed to have died out.
> http://www.mail-archive.com/kbuild-devel@lists.sourceforge.net/msg02487.html
>
> I also found a code repository 'menuconfig' here, although I doubt
> that this is an official one:
> http://code.google.com/p/menuconfig/source/browse/trunk/
>
> Specifically, I'd like to know:
> * are there 'official' sources to kbuild in some repository outside
> the linux kernel?
No, it is maintained as part of the kernel.
> * which steps are needed to use kbuild in a project other than the
> linux kernel? Is there some documentation available?
> * what is the license under which kbuild is distributed? In case it's
> GPL, does this impact the license of the software project using
> kbuild, i.e. does using kbuild imply the project being a derived work?
The license is GPLv2. Using kconfig as a separate tool to configure
options should probably be OK, I'm not so sure about using kbuild. You
should ask a lawyer. Or ask Kai Germaschewski and Sam Ravnborg if they
will sue you or not :-). Also see the first paragraph.
Michal
next prev parent reply other threads:[~2011-02-16 13:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 9:08 kbuild/kconfig for non-Linux projects Thomas De Schampheleire
2011-02-16 13:46 ` Michal Marek [this message]
2011-02-16 16:53 ` Arnaud Lacombe
2011-02-16 20:11 ` Sam Ravnborg
2011-02-18 15:55 ` Thomas De Schampheleire
-- strict thread matches above, loose matches on Subject: below --
2011-10-02 9:30 Alexander Kriegisch
2011-10-02 10:56 ` Alexander Kriegisch
2011-10-02 11:06 ` Yann E. MORIN
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=4D5BD54D.7070209@suse.cz \
--to=mmarek@suse.cz \
--cc=lacombar@gmail.com \
--cc=linux-kbuild@vger.kernel.org \
--cc=patrickdepinguin+kbuild@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox