Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [RFCv2] Per-package out-of-tree build
Date: Wed, 17 Apr 2013 18:33:54 +0200	[thread overview]
Message-ID: <516ECEF2.70307@mind.be> (raw)
In-Reply-To: <20130413205422.7eb87375@skate>

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.


  Regards,
  Arnout

-- 
Arnout Vandecappelle                          arnout at mind be
Senior Embedded Software Architect            +32-16-286500
Essensium/Mind                                http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium           BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint:  7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F

  parent reply	other threads:[~2013-04-17 16:33 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 [this message]
2013-04-18  7:26   ` Thomas Petazzoni

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=516ECEF2.70307@mind.be \
    --to=arnout@mind.be \
    --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