Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] using a local package file : why copy it to the dl directory ?
Date: Wed, 09 Oct 2013 18:02:28 +0200	[thread overview]
Message-ID: <52557E14.3040102@mind.be> (raw)
In-Reply-To: <22B9374628844ED0809C78AC328E71C5@JohanW7>

On 10/09/13 00:19, Sagaert Johan wrote:
> Hi
>
>
> 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 ?

  It seems the other two repliers missed your point :-)

  There is no fundamental need to copy it. However, it makes buildroot a 
lot simpler. In many places there are direct references to DL_DIR (just 
grep for that variable); in case of a file SITE_METHOD, you'd have to use 
$(PKG)_SITE instead of DL_DIR.

  It is possible to use hardlinking or symlinking instead of copying. 
Buildroot provides the BR2_LOCALFILES config option for that (in Build 
options -> Commands). Just set that to "ln" for hard linking or "ln -s" 
for symlinking.

  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-10-09 16:02 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
2013-10-08 23:12   ` Sagaert Johan
2013-10-09  0:06     ` Ryan Barnett
2013-10-09 16:02 ` Arnout Vandecappelle [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=52557E14.3040102@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