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] Building For Host as Target
Date: Thu, 3 May 2012 18:14:23 +0200	[thread overview]
Message-ID: <20120503181423.35715875@skate> (raw)
In-Reply-To: <CADwac6DA5MDVkfZDmAO-s2+rPsebpefJ-paTWLzkk0hC_qAOZg@mail.gmail.com>

Le Thu, 3 May 2012 18:14:49 +0300,
Assaf Inbal <shmuelzon@gmail.com> a ?crit :

> I'm working on a project based on buildroot and I want to have the
> ability to compile my packages for both my MIPS target using an
> external toolchain (which works great) but I also want to be able to
> compile for my host. To be precise, I want to use the local gcc and
> libraries so I will be able to run my packages locally as well.
> I've tried setting an external toolchain path as "/usr" but as a part
> of preparing the target file system everything from my /lib,/etc and
> others are copied to the output directory, which is, well, bad.
> 
> I've also toyed with creating a fake toolchain that was basically
> links to the host's binaries but that also didn't go very well.
> 
> Does anyone have an idea on how I might be able to achieve this?

If it's only for a reduced set of packages, you can implement the host
variant of those packages. They will be built with the native compiler
of your build machine, and will be installed in output/host.

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

  reply	other threads:[~2012-05-03 16:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-03 15:14 [Buildroot] Building For Host as Target Assaf Inbal
2012-05-03 16:14 ` Thomas Petazzoni [this message]
2012-05-03 20:14   ` Assaf Inbal
2012-05-03 21:17     ` Thomas Petazzoni
2012-05-03 22:18       ` Assaf Inbal
2012-05-03 18:08 ` Baruch Siach
2012-05-03 20:08   ` Assaf Inbal

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=20120503181423.35715875@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