All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv2] Per-package out-of-tree build
Date: Thu, 18 Apr 2013 09:26:44 +0200	[thread overview]
Message-ID: <20130418092644.19dcdf33@skate> (raw)
In-Reply-To: <516ECEF2.70307@mind.be>

Dear Arnout Vandecappelle,

On Wed, 17 Apr 2013 18:33:54 +0200, Arnout Vandecappelle wrote:
> On 13/04/13 20:54, Thomas Petazzoni wrote:
> >   * A <pkg>_SUPPORTS_OUT_OF_TREE variable defines whether the package
> >     supports out of tree build or not. By default, it's set to NO, in
> >     which case the package source code is rsynced from its source
> >     directory to the build directory at the beginning of the configure
> >     step. It is set to YES by both the autotools and cmake package
> >     infrastructures (which have been modified to do out of tree build),
> >     and by some packages that use the generic infrastructure but
> >     nonetheless support out of tree build.
> 
>   It may have been discussed before, but wouldn't it be more convenient 
> to insert an extra rsync step explicitly? Similar to how it's currently 
> done for OVERRIDE_SRCDIR.

Yes, I think it would make sense. I'll try to implement this (I have a
11 hours flight tomorrow, so plenty of time for BR hacking, don't
hesitate to give more feedback on this out of tree stuff).

Thanks,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2013-04-18  7:26 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-13 18:54 [Buildroot] [RFCv2] Per-package out-of-tree build Thomas Petazzoni
2013-04-14  5:55 ` Diego Iastrubni
2013-04-15  7:36   ` Thomas Petazzoni
2013-04-16 23:03 ` Cam Hutchison
2013-04-17  7:51   ` Thomas Petazzoni
2013-04-17 16:33 ` Arnout Vandecappelle
2013-04-18  7:26   ` Thomas Petazzoni [this message]

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=20130418092644.19dcdf33@skate \
    --to=thomas.petazzoni@free-electrons.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 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.