From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] arc: Add option for ARC-specific download site
Date: Mon, 22 Apr 2013 20:25:02 +0200 [thread overview]
Message-ID: <5175807E.2010503@mind.be> (raw)
In-Reply-To: <20130422174812.621ec3c4@skate>
On 22/04/13 17:48, Thomas Petazzoni wrote:
> Dear Mischa Jonker,
>
> On Mon, 22 Apr 2013 13:37:26 +0200, Mischa Jonker wrote:
>
>> >+config BR2_ARC_SITE
>> >+ string "Download site for ARC specific packages"
>> >+ default"http://www.synopsys.com/apps/arc-developer/"
>> >+ depends on BR2_arc || BR2_arceb
>> >+ help
>> >+ This download site is used for packages that require specific
>> >+ support for ARC, while this support is not yet pushed to the
>> >+ respective open source project.
> Is there some realistic case for which this URL would need to be
> changed by the user? I think I'd prefer to hardcode the URL in the
> binutils/gcc/uClibc recipes, just like we do a special casing for
> AVR32, unless of course there is some compelling reason for making this
> configurable.
+1 on that.
But it may make sense to define the base URL once in some .mk file and
use it in the other locations. You probably don't need to worry about the
order of .mk file inclusion because the variable will only be expanded
when a rule is executed, not when the .mk files are parsed. So it should
be safe to define it in e.g. the toolchain/gcc/gcc.mk and use it in binutils.
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
next prev parent reply other threads:[~2013-04-22 18:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-22 11:37 [Buildroot] [PATCH 0/7] RFC: ARC port Mischa Jonker
2013-04-22 11:37 ` [Buildroot] [PATCH 1/7] arc: Add ARC and ARC BE architecture Mischa Jonker
2013-04-22 15:47 ` Thomas Petazzoni
2013-04-22 18:40 ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 2/7] arc: Add option for ARC-specific download site Mischa Jonker
2013-04-22 15:48 ` Thomas Petazzoni
2013-04-22 18:25 ` Arnout Vandecappelle [this message]
2013-04-22 11:37 ` [Buildroot] [PATCH 3/7] arc: Add support for ARC-specific binutils Mischa Jonker
2013-04-22 15:49 ` Thomas Petazzoni
2013-04-22 18:35 ` Arnout Vandecappelle
2013-04-22 18:36 ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 4/7] arc: Add ARC specific kernel headers Mischa Jonker
2013-04-22 15:52 ` Thomas Petazzoni
2013-04-22 11:37 ` [Buildroot] [PATCH 5/7] arc: Add support for ARC-specific GCC Mischa Jonker
2013-04-22 15:56 ` Thomas Petazzoni
2013-04-24 12:44 ` Mischa Jonker
2013-04-24 14:27 ` Thomas Petazzoni
2013-04-24 15:19 ` Mischa Jonker
2013-04-24 21:19 ` Yann E. MORIN
2013-04-22 11:37 ` [Buildroot] [PATCH 6/7] arc: Add support for ARC-specific uClibc Mischa Jonker
2013-04-22 15:56 ` Thomas Petazzoni
2013-04-22 11:37 ` [Buildroot] [PATCH 7/7] arc: Make sure that libgcc doesn't get included when it doesn't exist yet Mischa Jonker
2013-04-22 15:57 ` Thomas Petazzoni
2013-04-22 15:46 ` [Buildroot] [PATCH 0/7] RFC: ARC port Thomas Petazzoni
2013-04-22 16:01 ` [Buildroot] Plan of libffi support? Thomas Petazzoni
2013-04-24 6:38 ` Mischa Jonker
2013-04-24 14:38 ` Thomas Petazzoni
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=5175807E.2010503@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