From: Jon Loeliger <jdl@bigfootnetworks.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "John W. Linville" <linville@tuxdriver.com>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Luis R. Rodriguez" <mcgrof@gmail.com>
Subject: Re: [PATCH CRDA] Introduce separate HOST and TARGET compilation steps.
Date: Tue, 30 Jun 2009 09:50:03 -0500 [thread overview]
Message-ID: <1246373403.13176.3.camel@jdl-desktop> (raw)
In-Reply-To: <1246345190.16256.1.camel@johannes.local>
On Tue, 2009-06-30 at 08:59 +0200, Johannes Berg wrote:
> On Mon, 2009-06-29 at 16:29 -0500, Jon Loeliger wrote:
> > The regdbdump tool is really a host executable that is used
> > during the build process. It could also be installed and
> > used on the target, but two separate compilations are needed
> > to achieve that goal.
> >
> > Currently, regdbdump is only built for the target, and thus
> > cross-compilation of the tool is really feasible without
> > this patch (or one like it).
>
> I don't think John is the correct addressee, Luis maintains this still,
Oh! Sorry!
> afaik. The only thing I'm not sure about is the separation into host/
> and target/,
Do you have another suggestion? Another approach would be to
leave the "target" stuff in the top-level directory straight up,
and bury the build of the host "tools" in a sub-directory?
> but otherwise this seems ok to me.
Thanks.
> johannes
jdl
next prev parent reply other threads:[~2009-06-30 14:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 21:29 [PATCH CRDA] Introduce separate HOST and TARGET compilation steps Jon Loeliger
2009-06-29 22:17 ` Pavel Roskin
2009-06-30 21:10 ` Jon Loeliger
2009-06-30 6:59 ` Johannes Berg
2009-06-30 14:50 ` Jon Loeliger [this message]
2009-06-30 16:12 ` Luis R. Rodriguez
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=1246373403.13176.3.camel@jdl-desktop \
--to=jdl@bigfootnetworks.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=mcgrof@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).