From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [EXT] Re: [PATCH v2 1/3] package/arm-gnu-rm-toolchain: new package
Date: Tue, 5 Feb 2019 11:32:19 +0100 [thread overview]
Message-ID: <20190205103219.GB18066@scaer> (raw)
In-Reply-To: <CAAXf6LX=T_hPz05g6vmkfHFpH4HKuGnTfxva7YJxJ4YX8tojog@mail.gmail.com>
Kostya, All,
On 2019-02-05 11:15 +0100, Thomas De Schampheleire spake thusly:
> El mar., 5 feb. 2019 a las 10:34, Kostya Porotchkin
> (<kostap@marvell.com>) escribi?:
[--SNIP--]
> > > > +define HOST_ARM_GNU_RM_TOOLCHAIN_INSTALL_CMDS
> > > > + mkdir -p $(HOST_DIR)/opt/gcc-arm-none-eabi/
> > > > + cp -a $(@D)/* $(HOST_DIR)/opt/gcc-arm-none-eabi/
> > >
> > > You should rather use a mv to avoid the size duplication, like we do in the
> > > external-toolchain infra for the main toolchain.
> > [KP] Yes, already doing so following Thomas review
Yeah, the guys were doing the review at the same tiem I was, I just got
sidetracked and did not notice before sending my mail. ;-)
> > > Also, why do you not install them in $(HOST_DIR)? As it is as you did, other
> > > packages have to know about this specific location, which is not entirely
> > > nice... However, if installing in $(HOST_DIR), maybe we have to be carefull
> > > about not causing name-clashing with other host stuff...
> > [KP] Again, after Thomas review I am adding symbolic links from the toolchain executables in "bin" folder to the $(HOST_DIR)/bin
> > Will it be enough? I am noty sure if it's good to just extract the entire package to the $(HOST_DIR)/.
> > Please correct me if I am wrong.
> Yes, I think that we should only have symlinks there, not the actual
> extracted tarball. This follows the same approach as the internal
> toolchain.
Yes, actually, symlinks will probably be enough, indeed. I was just
pointing out the usefulness of being able to call the tools from a known
location, even only if via symlinks.
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 561 099 427 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2019-02-05 10:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-05 7:43 [Buildroot] [PATCH 0/3] Support 32-bit code generation for Armv8 targets kostap at marvell.com
2019-02-05 7:43 ` [Buildroot] [PATCH v2 1/3] package/arm-gnu-rm-toolchain: new package kostap at marvell.com
2019-02-05 8:46 ` Arnout Vandecappelle
2019-02-05 8:48 ` Thomas De Schampheleire
2019-02-05 8:52 ` [Buildroot] [EXT] " Kostya Porotchkin
2019-02-05 9:19 ` [Buildroot] " Yann E. MORIN
2019-02-05 9:34 ` [Buildroot] [EXT] " Kostya Porotchkin
2019-02-05 10:15 ` Thomas De Schampheleire
2019-02-05 10:32 ` Yann E. MORIN [this message]
2019-02-05 7:43 ` [Buildroot] [PATCH v2 2/3] boot: a3700-utils-marvell: Add Armada-3700 utilities kostap at marvell.com
2019-02-05 7:43 ` [Buildroot] [PATCH v2 3/3] boot: arm-trusted-firmware: add support for Marvell Armada 3700 kostap at marvell.com
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=20190205103219.GB18066@scaer \
--to=yann.morin.1998@free.fr \
--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