From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Source download overwrite
Date: Fri, 14 Nov 2014 15:33:10 +0100 [thread overview]
Message-ID: <20141114153310.354a7c24@free-electrons.com> (raw)
In-Reply-To: <CAOFH_kHZD-1aq31owR-D5GC_stX+zoGPiHyE1aovLGt6WZiOZw@mail.gmail.com>
Dear Mathieu Slabbinck,
On Fri, 14 Nov 2014 15:27:43 +0100, Mathieu Slabbinck wrote:
> Thomas,
>
> thanks for pointing this out. Was looking for this kind of variable but
> didn't really find any docs about it.
I just checked, and at
http://buildroot.org/downloads/manual/manual.html#_infrastructure_for_packages_with_specific_build_systems,
under the section "16.5.2. generic-package reference", we do document
the EXTRA_DOWNLOADS variable:
"""
LIBFOO_EXTRA_DOWNLOADS lists a number of additional files that
Buildroot should download from LIBFOO_SITE in addition to the main
LIBFOO_SOURCE (which usually is a tarball). Buildroot will not do
anything with those additional files, except download files: it will be
up to the package recipe to use them from $(BR2_DL_DIR).
"""
Though I agree the manual is now very long, and it is easy to overlook
certain possibilities provided by Buildroot.
> Managed to get it working now.
Cool!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2014-11-14 14:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-14 9:24 [Buildroot] Source download overwrite Mathieu Slabbinck
2014-11-14 13:14 ` Thomas Petazzoni
2014-11-14 14:27 ` Mathieu Slabbinck
2014-11-14 14:33 ` Thomas Petazzoni [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=20141114153310.354a7c24@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