From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] Make external toolchain relocatable
Date: Sun, 15 Jul 2012 13:16:40 +0200 [thread overview]
Message-ID: <5002A698.6030808@mind.be> (raw)
In-Reply-To: <CAHXCMMKEWFS82V0wGLGD4Le66zKzGHs2UHd2bzxEvwU7bPbo3A@mail.gmail.com>
On 07/07/12 23:18, Samuel Martin wrote:
> Hi Arnout, all,
>
> 2012/6/30 Arnout Vandecappelle (Essensium/Mind)<arnout@mind.be>:
> > The external toolchain wrapper sets sysroot etc. to an absolute path.
> > By changing this to a relative path, it is possible to move the host
> > directory to a different location and still have a working build
> > system.
>
> I've just tested your patch on top of my branch, it seems working well
> but doesn't do all the job.
> You have probably focused on the wrapper code and forgot to update
> target of the symlinks of all other tools, pointing to the relative
> location of them instead of the absolute one.
I just sent a v3. Care to test it again?
> > This only works for a downloaded external toolchain. For a pre-installed
> > external toolchain, it is possible to move the host directory to a
> > different location, but not the external toolchain directory (it does work
> > if the external toolchain directory lies within the host directory). For
> > an internal or crosstool-ng toolchain, there is no wrapper so updating the
> > sysroot path should be done in a different way.
>
> For internal and crosstool-ng toolchains, I think if we want to ensure
> the tools are called with the correct sysroot argument, tehn we should
> use the wrapper too.
Good idea. But then it should be installed in a different place as well. But
on the other hand, we don't want to go and copy the sysroot directory for
internal/crosstool-NG toolchains... Bottom line: I'm not going to try it :-)
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286540
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
prev parent reply other threads:[~2012-07-15 11:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-30 20:22 [Buildroot] [PATCH v2] Make external toolchain relocatable Arnout Vandecappelle
2012-07-07 21:18 ` Samuel Martin
2012-07-15 11:16 ` Arnout Vandecappelle [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=5002A698.6030808@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.