Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernhard Reutner-Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] RFC: option to Makefile.autotools.in to build in	$(PROJECT_BUILD_DIR)
Date: Thu, 19 Feb 2009 12:33:20 +0100	[thread overview]
Message-ID: <20090219113320.GB1829@mx.loc> (raw)
In-Reply-To: <87wsbmad7g.fsf@macbook.be.48ers.dk>

On Thu, Feb 19, 2009 at 12:16:51PM +0100, Peter Korsgaard wrote:
>>>>>> "Hamish" == Hamish Moffatt <hamish@cloud.net.au> writes:
>
>Hi,
>
> Hamish> I've got a package which will use Makefile.autotools.in that
> Hamish> needs to build in $(PROJECT_BUILD_DIR), because it builds
> Hamish> kernel modules.
>
> Hamish> Here is my proposed patch to Makefile.autotools.in to support
> Hamish> this (via a FOO_BUILD_PROJECT_DIR = YES/NO option). Feedback
> Hamish> welcome; unless there's issues I will commit in a day or two.
>
>It adds a lot of clutter, but I also don't see any other way of doing
>it. We could change the user interface to be something like
>FOO_BUILD_DIR (defaulting to BUILD_DIR), and use it in the
>
>$(2)_DIR                        =  $$(BUILD_DIR)/$(1)-$$($(2)_VERSION)
>
>line - But that probably buys us very little.

I admit that i didn't look but it sounds a bit like you would want to
do the same like i did for THIS_SRCDIR (THIS_BUILDDIR comes to mind).
HTH,

  reply	other threads:[~2009-02-19 11:33 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-17  5:02 [Buildroot] RFC: option to Makefile.autotools.in to build in $(PROJECT_BUILD_DIR) Hamish Moffatt
2009-02-19 11:16 ` Peter Korsgaard
2009-02-19 11:33   ` Bernhard Reutner-Fischer [this message]
2009-02-19 12:14     ` Peter Korsgaard
2009-02-19 12:34       ` Bernhard Reutner-Fischer
2009-02-19 12:43         ` Peter Korsgaard
2009-02-19 23:39           ` Hamish Moffatt

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=20090219113320.GB1829@mx.loc \
    --to=rep.dot.nop@gmail.com \
    --cc=buildroot@busybox.net \
    /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