From: Gerd Hoffmann <kraxel@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Re: [PATCH] Compile usb_ohci only for targets that need it
Date: Wed, 26 Aug 2009 12:28:22 +0200 [thread overview]
Message-ID: <4A950E46.6030404@redhat.com> (raw)
In-Reply-To: <m3fxbe6fui.fsf@neno.mitica>
Hi,
> default-configs/<target_name>
ok.
> <target_name>/config-devices.mak
target name == x86_64-softmmu, i.e. build tree (with separate
source/build trees)?
> if it don't exist, it get copied from default-configs/<target_name> one
configure can copy stuff for now, so you can do:
mkdir build-myconfig
cd build-myconfig
../configure --target-list=x86_64-softmmu
vi x86_64-softmmu/config-devices.mak
make
later on we can replace the 'vi' step with something more clever.
cheers,
Gerd
prev parent reply other threads:[~2009-08-26 10:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-25 18:16 [Qemu-devel] [PATCH] Compile usb_ohci only for targets that need it Juan Quintela
2009-08-26 10:04 ` Gerd Hoffmann
2009-08-26 10:13 ` [Qemu-devel] " Juan Quintela
2009-08-26 10:15 ` Juan Quintela
2009-08-26 10:28 ` Gerd Hoffmann [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=4A950E46.6030404@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.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).