From: Pavel Roskin <proski@gnu.org>
To: Jon Loeliger <jdl@bigfootnetworks.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: RFC: cross-building crda
Date: Thu, 11 Jun 2009 18:51:25 -0400 [thread overview]
Message-ID: <1244760685.6544.6.camel@mj> (raw)
In-Reply-To: <1244733695.14768.22.camel@jdl-desktop>
On Thu, 2009-06-11 at 10:21 -0500, Jon Loeliger wrote:
> So I'm proposing to introduce a two-layer build where the
> top-level Makefile will introduce a "host/" and a "target/"
> sub-directory build for each environment. If the build
> is not a cross-build, no "target/" build happens and it
> all gets built in "host/" only. The C files and sources
> all stay in the current top-level directory, and will be
> referenced and built into the host/ and target/ through
> Makefile fidgery sub-directories.
This sounds too complicated. No other popular software does it, yet
somehow it can be cross-compiled. I'm not talking about such software
as kernels, compilers and other tools that need to know specific
characteristics of the target.
Please check the sources of buildroot (http://buildroot.uclibc.org/) to
see how it manages to cross-compile a lot of programs that don't do
anything specific to support cross-compilation. Sometimes minimal
patches are needed, but nothing nearly as intrusive as your proposal.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-06-11 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-11 15:21 RFC: cross-building crda Jon Loeliger
2009-06-11 22:51 ` Pavel Roskin [this message]
2009-06-12 21:37 ` Jon Loeliger
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=1244760685.6544.6.camel@mj \
--to=proski@gnu.org \
--cc=jdl@bigfootnetworks.com \
--cc=linux-wireless@vger.kernel.org \
/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.