From: "David Byron" <dbyron@hheld.com>
To: "'Josh Boyer'" <jwboyer@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: RE: autoconf for mtd-utils
Date: Tue, 1 Aug 2006 12:25:19 -0700 [thread overview]
Message-ID: <000001c6b5a0$3a0a5bb0$c834800a@RudiDell> (raw)
In-Reply-To: AAAAAJOKoN+ryO5OkOyypB2eX+7EESIA
On Mon, 2006-07-31 at 5:50p, Josh Boyer wrote:
> Better. But it only defines BUILDDIR during a cross compile. Is that
> what you wanted? Or did you want a general purpose way to separate
> the object and binary files from the source during build time?
I do define BUILDDIR for native builds too, but to the current directory.
The important thing for me is that native objects live in a different place
than cross-compiled objects. Where they are relative to the source isn't
important to me at the moment.
-DB
next reply other threads:[~2006-08-01 19:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-01 19:25 David Byron [this message]
2006-08-02 11:00 ` autoconf for mtd-utils Josh Boyer
2006-08-03 12:22 ` Josh Boyer
-- strict thread matches above, loose matches on Subject: below --
2006-07-31 17:47 David Byron
2006-08-01 0:50 ` Josh Boyer
2006-07-19 21:37 David Byron
2006-07-30 18:09 ` Josh Boyer
2006-07-19 18:52 David Byron
2006-07-19 19:24 ` David Woodhouse
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='000001c6b5a0$3a0a5bb0$c834800a@RudiDell' \
--to=dbyron@hheld.com \
--cc=jwboyer@gmail.com \
--cc=linux-mtd@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox