All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Suggestion to improving buildroot download infra
Date: Wed, 15 Nov 2017 15:50:26 +0100	[thread overview]
Message-ID: <20171115155026.69153059@windsurf.lan> (raw)
In-Reply-To: <5A0C4958.9040608@petroprogram.com>

Hello,

On Wed, 15 Nov 2017 16:04:08 +0200, Stefan Fr?berg wrote:

> Is there a way to integrate parallel wget download into buildroot?

This will be a direct consequence of top-level parallel build support.
Not only parallel download, but downloading package A, while package B
is being built, etc.

> That would greatly speed the downloading process when doing "make source"
> and maybe even later all the downloading could be done in the 
> background, even
> when compiling some big package (for example, gentoo linux does that).
> 
> If I understand it correctly, there are at least two (if not including 
> the crude & fork method)
> ways to do parallel wget:
> 
> 1. use xarg:
> 
> echo $URL_LIST | xargs -n 1 -P ${NUMBER_OF_PARALLEL_DOWNLOADS} wget
> 
> or 2. use GNU parallel
> 
> parallel -a $URL_LIST --jobs ${NUMBER_OF_PARALLEL_DOWNLOADS} wget
> 
> How exactly, does buildroot collect the download urls when doing example,
> "make source" ? Does it collect them first into some list and then do 
> wget -i list ?
> Or does it just go each selected packet one-by-one and fetch the url for 
> each?

For the moment, the easiest is to comment the .NOTPARALLEL: statement
in the main Makefile, and then run:

	make -j8 source

Best regards,

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

  reply	other threads:[~2017-11-15 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 14:04 [Buildroot] Suggestion to improving buildroot download infra Stefan Fröberg
2017-11-15 14:50 ` Thomas Petazzoni [this message]
2017-11-15 18:40   ` Stefan Fröberg
2017-11-15 21:24 ` 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=20171115155026.69153059@windsurf.lan \
    --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.