From: Sam Ravnborg <sam@ravnborg.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kai Germaschewski <kai@germaschewski.name>,
Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Development <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] out-of-tree builds
Date: Mon, 15 Mar 2004 19:02:47 +0100 [thread overview]
Message-ID: <20040315180243.GB8456@mars.ravnborg.org> (raw)
In-Reply-To: <Pine.GSO.4.58.0403141353470.1231@waterleaf.sonytel.be>
On Sun, Mar 14, 2004 at 01:58:36PM +0100, Geert Uytterhoeven wrote:
>
> Although I like the feature to build a kernel in a different directory a lot, I
> don't like its syntax. I prefer to just have a build directory where I can run
> `make whatever'.
>
> The following patch adds a configure script to the kernel. If you run
>
> /path/to/kernel/source/tree/configure
>
> it will create a Makefile in the current directory, after which you can just do
> `make whatever', just like in the source directory.
>
> The configure script contains a simple protection for when run in the source
> directory, but this may be approved (I'm not a configure script guru).
>
> Comments?
I like the general idea.
I'm in doubt that configure is the best name, because no actual
configuration takes place.
But I want to finish the external modules stuff before introducing
more features. So it will wait until then.
Sam
next prev parent reply other threads:[~2004-03-15 18:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-14 12:58 Geert Uytterhoeven
2004-03-15 9:26 ` Geert Uytterhoeven
2004-03-15 12:41 ` Geert Uytterhoeven
2004-03-15 17:58 ` Sam Ravnborg
2004-03-15 18:04 ` Geert Uytterhoeven
2004-03-22 22:09 ` Geert Uytterhoeven
2004-04-01 9:35 ` Geert Uytterhoeven
2004-03-15 18:02 ` Sam Ravnborg [this message]
2004-03-22 22:11 ` Geert Uytterhoeven
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=20040315180243.GB8456@mars.ravnborg.org \
--to=sam@ravnborg.org \
--cc=geert@linux-m68k.org \
--cc=kai@germaschewski.name \
--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®