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] using a local package file : why copy it to the dl directory ?
Date: Wed, 9 Oct 2013 00:23:31 +0200	[thread overview]
Message-ID: <20131009002331.5e89e31a@skate> (raw)
In-Reply-To: <22B9374628844ED0809C78AC328E71C5@JohanW7>

Dear Sagaert Johan,

On Wed, 9 Oct 2013 00:19:12 +0200, Sagaert Johan wrote:

> I noticed when using SITE_METHOD = file, the package is copied to the download directory.
> Is this needed, since the package is already on our local filesystem ?

Yes it is needed, because:

 (1) Buildroot do not want to make changes outside of its output
     directory. We clearly do not want Buildroot to mess up with your
     source directory, and create its stamp files, and the result of
     the compilation there.

 (2) Buildroot does not use out of tree build for packages. If it was
     using out of tree build, then we could avoid that copy by using
     your local directory as the source tree, and the
     output/build/<pkgname>-<pkgversion> directory as the build tree. A
     while ago, I started working on out-of-tree build for packages,
     precisely to improve this situation. See
     http://lists.busybox.net/pipermail/buildroot/2013-April/070573.html.
     It is certainly not impossible to do, but quite a huge patch set,
     with a lot of implications. Basically, my stuff was working in the
     general case, but there were some issues here and there that
     remained to be sorted out.

Best regards,

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

  reply	other threads:[~2013-10-08 22:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-08 22:19 [Buildroot] using a local package file : why copy it to the dl directory ? Sagaert Johan
2013-10-08 22:23 ` Thomas Petazzoni [this message]
2013-10-08 23:12   ` Sagaert Johan
2013-10-09  0:06     ` Ryan Barnett
2013-10-09 16:02 ` Arnout Vandecappelle

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=20131009002331.5e89e31a@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox