From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] toolchain: add a harmless link when sysroot detection is not accurate
Date: Sun, 1 May 2016 13:59:43 +0200 [thread overview]
Message-ID: <20160501135943.6e4d4f40@free-electrons.com> (raw)
In-Reply-To: <a96a4788-f871-3fe0-4887-29d77489dc73@gmail.com>
Hello,
On Sat, 30 Apr 2016 21:27:33 +0200, Romain Naour wrote:
> >> Well, the whole point for this patch [1] was to get rid of that hook (which was
> >> the first approach when I sent the patches to add the Codescape toolchains) and
> >> add that functionality in the toolchain infra just in case more toolchains with
> >> this problem were added in the future.
> >
> > I understand, let see what maintainers says.
>
> Like for CodeSourcery AArch64 toolchain recently [1], what about adding a
> post-install hook instead ?
>
> [1]
> https://git.busybox.net/buildroot/commit/?id=4d39ca1c2ab19766abf0430abe9b65ba0e16602b
Yeah, I don't know. There's a trade-off here:
- By having the logic in the common external toolchain logic, it's
usually more complicated, but at least it works for "custom"
external toolchains as well.
- By having a custom logic only for this toolchain, it's usually much
simpler, but it doesn't work for custom external toolchains.
Not easy to decide which approach is the most appropriate.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2016-05-01 11:59 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-22 15:05 [Buildroot] [PATCH v2] toolchain: add a harmless link when sysroot detection is not accurate Vicente Olivert Riera
2016-02-02 10:57 ` Vicente Olivert Riera
2016-02-02 14:21 ` Romain Naour
2016-02-02 15:14 ` Vicente Olivert Riera
2016-02-02 15:30 ` Romain Naour
2016-04-30 19:27 ` Romain Naour
2016-05-01 11:59 ` 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=20160501135943.6e4d4f40@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