From: "Zhang Haoyu" <zhanghy@sangfor.com>
To: qemu-devel <qemu-devel@nongnu.org>
Subject: [Qemu-devel] [question] qemu-2.0.0 difference between download from http://wiki.qemu.org/Download and download http://git.qemu.org/qemu.git
Date: Sat, 16 Aug 2014 10:24:46 +0800 [thread overview]
Message-ID: <201408161024436893152@sangfor.com> (raw)
Hi,
I download one copy of qemu-2.0.0 from http://wiki.qemu.org/Download,
and then download another copy of qemu-2.0.0 from http://git.qemu.org/qemu.git,
I compared them, found that dtc, pixman, roms are missed in the latter.
so If want to use qemu-2.0.1 to build my emulator,
should I still add these external libs/sources (incorporated in the qemu-2.0.0 from http://wiki.qemu.org/Download) to qemu-2.0.1 to build the emulator?
Thanks,
Zhang Haoyu
next reply other threads:[~2014-08-16 2:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 2:24 Zhang Haoyu [this message]
2014-08-16 18:01 ` [Qemu-devel] [question] qemu-2.0.0 difference between download from http://wiki.qemu.org/Download and download http://git.qemu.org/qemu.git Peter Maydell
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=201408161024436893152@sangfor.com \
--to=zhanghy@sangfor.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).