Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Can't use output/host/ as "SDK" with external toolchain
Date: Thu, 12 Jan 2012 10:17:30 +0100	[thread overview]
Message-ID: <20120112101730.472c6e92@skate> (raw)
In-Reply-To: <CAJpxd07HP8j=A15yW-PKg_SbMVw3tCeMvTodx2BdcCjR7-7rmQ@mail.gmail.com>

Hello Bryce,

Le Mon, 9 Jan 2012 14:54:13 -0800,
Bryce Schober <bryce.schober@gmail.com> a ?crit :

> What I mean by "SDK" is the ability to compile external programs
> using the buildroot toolchain and libraries on any
> reasonably-compatible host. I'm assuming that the toolchain itself is
> built properly static for its own host independence (which in my
> case, it is). Ideally the toolchain in the output/host directory
> would be capable of standing alone, when built properly
> 
> I'm having two issues w/ archving the output/host dir for extraction
> and usage in a different host directory. I'm using a custom-built
> crosstool-ng built externally and independent of buildroot.

As Peter has mentioned, moving the "SDK" to a different directory is
currently not supported. It has been discussed during our last meeting
in Prague, we listed the different things that we think need to be
fixed, but the work hasn't been done yet.

The meeting report that Peter has mentioned lists the different issues
that need to be fixed. So if you want to help, feel free to start with
this list :)

Those items are also on my TODO-list, but that one is so long that I
can't guarantee when I'll be able to do it.

Best regards,

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      parent reply	other threads:[~2012-01-12  9:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 22:54 [Buildroot] Can't use output/host/ as "SDK" with external toolchain Bryce Schober
2012-01-10 11:26 ` Thomas De Schampheleire
2012-01-10 20:22   ` Bryce Schober
2012-01-11  7:38     ` Thomas De Schampheleire
2012-01-11 14:19       ` Michael S. Zick
2012-01-11 19:49       ` Bryce Schober
2012-01-11 23:03         ` Peter Korsgaard
2012-01-12  9:17 ` 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=20120112101730.472c6e92@skate \
    --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