Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Report from the Buildroot Meeting in Berlin
Date: Mon, 24 Oct 2016 09:25:46 +0200	[thread overview]
Message-ID: <20161024092546.21e4dc0f@free-electrons.com> (raw)
In-Reply-To: <20161024005421.GA2747@tungsten.ozlabs.ibm.com>

Hello,

On Mon, 24 Oct 2016 11:54:23 +1100, Sam Bobroff wrote:

> >  - Improving the developer experience when using _OVERRIDE_SRCDIR or
> >    "local" packages. Currently, since the source code is copied in the
> >    build directory, the build errors and warnings refers to the build
> >    directory. That's not convenient for users running an IDE, since
> >    clicking on the warning or error does not bring to the correct
> >    file. After much discusion, it appears that the only reasonable
> >    solution is to implement per-package out-of-tree build.  
> 
> Great! Will this allow the use of --delete with the rsync that copies the
> source? (It would fix the problem caused by certain moved/renamed files in your
> source directory when using _OVERRIDE_SOURCEDIR.)

Well, if we have per-package out-of-tree, then there is no rsync at all
anymore. The source code stays in the directory specified in
_OVERRIDE_SRCDIR, and only the build tree is in
output/build/<pkg>-<version>/.

However, this obviously works only for packages that use a sane build
system supporting out of tree build.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com

  reply	other threads:[~2016-10-24  7:25 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-10-19 20:10 [Buildroot] Report from the Buildroot Meeting in Berlin Thomas Petazzoni
2016-10-20 16:39 ` Arnout Vandecappelle
2016-10-21  8:25   ` Thomas Petazzoni
2016-10-21  8:57     ` Arnout Vandecappelle
2016-10-21  9:05       ` Thomas Petazzoni
2016-10-24 12:02   ` Peter Korsgaard
2016-10-24 12:19     ` Vicente Olivert Riera
2016-10-24 12:28       ` Thomas Petazzoni
2016-10-24 13:05         ` Arnout Vandecappelle
2016-10-24 14:52           ` Vicente Olivert Riera
2016-10-24 14:57             ` Thomas Petazzoni
2016-10-24 15:47               ` [Buildroot] Toolchain wrapper CFLAGS [was: Re: Report from the Buildroot Meeting in Berlin] Arnout Vandecappelle
2016-10-24 12:39       ` [Buildroot] Report from the Buildroot Meeting in Berlin Peter Korsgaard
2016-10-24  0:54 ` Sam Bobroff
2016-10-24  7:25   ` Thomas Petazzoni [this message]
2016-10-25  2:21     ` Sam Bobroff

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=20161024092546.21e4dc0f@free-electrons.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox