From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building For Host as Target
Date: Thu, 3 May 2012 23:17:26 +0200 [thread overview]
Message-ID: <20120503231726.25b32670@skate> (raw)
In-Reply-To: <1654518205551106600@unknownmsgid>
Le Thu, 3 May 2012 23:14:30 +0300,
Assaf Inbal <shmuelzon@gmail.com> a ?crit :
> While host variants will run, it means that I still need to compile
> for some target platform. The output in the host directory will also
> include many other things not needed. Unless someone will come up
> with a better idea, I'm considering creating a new toolchain type
> (along side with buildroot and "external"). If I'll be pleased with
> the result I'll post a patch.
I am really not sure to understand what your use case is. The principle
of Buildroot is to generate an embedded Linux for a target platform
that has a different CPU architecture than the build platform, and
Buildroot uses cross-compilation to achieve this. If you're outside
this basic principle of Buildroot, I would probably say that Buildroot
isn't the right tool for the job you're trying to do.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2012-05-03 21:17 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
2012-05-03 20:14 ` Assaf Inbal
2012-05-03 21:17 ` Thomas Petazzoni [this message]
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=20120503231726.25b32670@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 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.