From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] support/scripts: add script to test a package
Date: Mon, 6 Feb 2017 21:43:44 +0100 [thread overview]
Message-ID: <20170206214344.3bfd403d@free-electrons.com> (raw)
In-Reply-To: <508724e1-501e-4e44-6817-55bcdbf2f8ee@lucaceresoli.net>
Hello,
On Mon, 6 Feb 2017 21:40:58 +0100, Luca Ceresoli wrote:
> Splitting the source step from the build step is nice since it clearly
> separated download-related issues (wrong URL, network down...) from
> build errors.
>
> But as discussed IRL it also means we download the ACTUAL_SOURCE files,
> which means hundreds of megabytes with external toolchains. Possible
> solutions:
>
> * remove the "make source" step and let "make ${pkg}" download only the
> sources that are really needed for building
> * remove the "make source" step as above, but only if ${pkg} is empty
> * add a "source-only-filed-needed-for-build" :) target and use that
I don't really see the need for separating the build step from the
source step in this script. Why not just do the build, and that's it?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-06 20:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-06 18:02 [Buildroot] [PATCH] support/scripts: add script to test a package Yann E. MORIN
2017-02-06 20:40 ` Luca Ceresoli
2017-02-06 20:43 ` Thomas Petazzoni [this message]
2017-02-06 20:59 ` Luca Ceresoli
2017-02-07 9:33 ` Yann E. MORIN
2017-02-07 10:48 ` Luca Ceresoli
2017-02-07 14:41 ` Peter Korsgaard
2017-02-07 14:46 ` Yann E. MORIN
2017-02-06 20:44 ` Thomas De Schampheleire
2017-02-07 9:52 ` Yann E. MORIN
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=20170206214344.3bfd403d@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 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.