From: Jon Loeliger <jdl@bigfootnetworks.com>
To: Samuel Ortiz <samuel@sortiz.org>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Cross compiling libnl, iw, crda and friends
Date: Wed, 10 Jun 2009 09:59:55 -0500 [thread overview]
Message-ID: <1244645995.14768.6.camel@jdl-desktop> (raw)
In-Reply-To: <1244587813.2628.10.camel@sortiz-mobl>
On Wed, 2009-06-10 at 00:50 +0200, Samuel Ortiz wrote:
> Hi Jon,
>
> On Tue, 2009-06-09 at 14:54 -0500, Jon Loeliger wrote:
> > Guys,
> >
> > Am I missing an obvious solution to cross compiling libnl, iw,
> > the crda and related friends?
> >
> Unless you're looking for a quick and easy fix to build some
> one-shot demo image for your target, you may want to start looking
> at cross platform build systems, like openembedded, poky or maybe
> openwrt.
>
> Cheers,
> Samuel.
Hi folks,
Thanks for the feedback. I totally get the cross-compilation
environment thing, thanks. I have all that set up. (PowerPC,
LTIB, powerpc-e300-linux-gnu-, etc.)
My questions really pertain to the actual configure and makefile
mechanisms in these packages themselves. For example, it seems
to me that the whole pkg-config mechanism as used in these
makefiles doesn't distinguish between the build and target include
directories.
I'll try and work up some patches.
Thanks,
jdl
prev parent reply other threads:[~2009-06-10 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-09 19:54 Cross compiling libnl, iw, crda and friends Jon Loeliger
2009-06-09 20:00 ` John W. Linville
2009-06-09 21:04 ` Felix Fietkau
2009-06-09 21:47 ` Alexandre Becholey - s h o c k f i s h /
2009-06-09 22:50 ` Samuel Ortiz
2009-06-10 14:59 ` Jon Loeliger [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=1244645995.14768.6.camel@jdl-desktop \
--to=jdl@bigfootnetworks.com \
--cc=linux-wireless@vger.kernel.org \
--cc=samuel@sortiz.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.