Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Add support for MIPS Codescape MTI GNU Linux toolchain
Date: Fri, 24 Jul 2015 01:06:55 +0200	[thread overview]
Message-ID: <55B1738F.9080805@imgtec.com> (raw)
In-Reply-To: <20150723221000.GB3530@free.fr>

Hello Yann,

On 24/07/15 00:10, Yann E. MORIN wrote:
> Still, I ahve a question for Thomas...
>
>> diff --git a/toolchain/toolchain-external/toolchain-external.mk b/toolchain/toolchain-external/toolchain-external.mk
>> index 5ce4d33..f762dbc 100644
>> --- a/toolchain/toolchain-external/toolchain-external.mk
>> +++ b/toolchain/toolchain-external/toolchain-external.mk
>> @@ -144,6 +144,8 @@ endif
>>   else
>>   ifeq ($(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2014R1)$(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2013R1)$(BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2012R2),y)
>>   TOOLCHAIN_EXTERNAL_BIN := $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/$(TOOLCHAIN_EXTERNAL_PREFIX)/bin
>> +else ifeq ($(BR2_TOOLCHAIN_EXTERNAL_CODESCAPE_MTI_MIPS201506),y)
>> +TOOLCHAIN_EXTERNAL_BIN := $(TOOLCHAIN_EXTERNAL_INSTALL_DIR)/2015.06-03/bin
>
> I wonder if we could not just use the _STRIP_COMPONENTS variable to get
> rid of that extra level...

That only work for regular packages living under $(TOPDIR)/package/.

I will send a patch to add the _STRIP_COMPONENTS for external 
toolchains, and then I will send a v3 of this one.

Regards,

Vincent.

  reply	other threads:[~2015-07-23 23:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23 18:19 [Buildroot] [PATCH v2] Add support for MIPS Codescape MTI GNU Linux toolchain Vicente Olivert Riera
2015-07-23 22:10 ` Yann E. MORIN
2015-07-23 23:06   ` Vicente Olivert Riera [this message]
2015-07-23 23:13     ` Vicente Olivert Riera

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=55B1738F.9080805@imgtec.com \
    --to=vincent.riera@imgtec.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