All of lore.kernel.org
 help / color / mirror / Atom feed
From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] Make external toolchain relocatable
Date: Mon, 16 Jul 2012 23:07:02 +0200	[thread overview]
Message-ID: <CAHXCMMJ8FRbEHGY-Aq8NifiFXaBTjNUP8+d=S0a2q2BNw-RAYA@mail.gmail.com> (raw)
In-Reply-To: <1342350726-29970-1-git-send-email-arnout@mind.be>

2012/7/15 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.
>
> 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.
>
> See http://lists.busybox.net/pipermail/buildroot/2012-February/050371.html
> for information about others things to do to make the host directory
> relocatable.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Acked-by: Samuel Martin <s.martin49@gmail.com>

Also tested.

  reply	other threads:[~2012-07-16 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-15 11:12 [Buildroot] [PATCH v3] Make external toolchain relocatable Arnout Vandecappelle
2012-07-16 21:07 ` Samuel Martin [this message]
2013-02-05 14:16 ` Peter Korsgaard

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='CAHXCMMJ8FRbEHGY-Aq8NifiFXaBTjNUP8+d=S0a2q2BNw-RAYA@mail.gmail.com' \
    --to=s.martin49@gmail.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 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.