From: Tim Walker <tim@astolat-it.co.uk>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Build environment image
Date: Fri, 24 Jun 2005 22:30:40 +0100 [thread overview]
Message-ID: <42BC7B80.2050803@astolat-it.co.uk> (raw)
In-Reply-To: <1119644713.766.9.camel@aragorn>
Thanks for the replies.
I thought the Live CD was a bad idea until I realised it can still be
booted under QEMU for non x86 users (Live CDs can be created for other
platforms - have to pick one otherwise it'd be a nightmare). The
tradeoff would be speed for x86 users vs ease of image maintenance and
build environment precision (host processor). There is an appealing
match between the desired uniformity of build environment and QEMU's aim
to uniformly emulate different platforms regardless of host. It could
also be a good test of QEMU itself in the same way GCC self compiles.
Cross compile to Windows from Linux is an unknown quantity to me - has
anyone tried it yet with QEMU?
Depending on how it's used this could either be a two edged sword or a
virtuous circle - headlines of "Convenient Build Environment demands
massive investment of time to keep functional" or "Convenient Build
Environment helps find QEMU inconsistencies and vice versa". Something
like that.
Cheers,
Tim
next prev parent reply other threads:[~2005-06-24 21:31 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-19 19:09 [Qemu-devel] quick gtk2.c update Jim C. Brown
2005-06-19 22:25 ` Sebastien Bechet
2005-06-20 0:01 ` Jim C. Brown
2005-06-19 22:57 ` jeebs
2005-06-19 23:53 ` Jim C. Brown
[not found] ` <002c01c57535$60064fb0$334d21d1@organiza3bfb0e>
2005-06-20 1:59 ` Jim C. Brown
2005-06-21 2:27 ` jeebs
2005-06-21 2:39 ` Jim C. Brown
2005-06-21 2:58 ` jeebs
2005-06-21 4:28 ` Jim C. Brown
2005-06-21 10:45 ` Jernej Simončič
2005-06-21 16:27 ` jeebs
2005-06-21 17:20 ` Jernej Simončič
2005-06-21 19:40 ` jeebs
2005-06-21 20:22 ` Jernej Simončič
2005-06-21 21:19 ` jeebs
2005-06-21 22:24 ` Jim C. Brown
2005-06-21 22:45 ` jeebs
2005-06-21 23:58 ` Jim C. Brown
2005-06-22 4:14 ` jeebs
2005-06-22 5:15 ` Damien Mascord
2005-06-22 9:31 ` Jernej Simončič
2005-06-22 12:31 ` Jim C. Brown
2005-06-22 9:16 ` Jernej Simončič
2005-06-22 13:17 ` Jim C. Brown
2005-06-22 18:36 ` Jim C. Brown
2005-06-22 18:53 ` Jim C. Brown
2005-06-22 20:59 ` Jim C. Brown
2005-06-23 2:26 ` jeebs
2005-06-24 0:32 ` Jim C. Brown
2005-06-26 16:13 ` Jim C. Brown
2005-06-27 17:11 ` jeebs
2005-06-27 18:15 ` Jim C. Brown
2005-06-22 13:22 ` Jim C. Brown
2005-06-22 3:53 ` Herbert Poetzl
2005-06-22 12:41 ` Jim C. Brown
2005-06-21 21:52 ` Jim C. Brown
2005-06-21 19:45 ` Jim C. Brown
2005-06-21 20:32 ` [Qemu-devel] Build environment image Tim Walker
2005-06-24 17:19 ` Tim Walker
2005-06-24 17:48 ` John R. Hogerhuis
2005-06-24 18:24 ` Christian MICHON
2005-06-24 18:41 ` John R. Hogerhuis
2005-06-24 18:41 ` Christian MICHON
2005-06-24 19:09 ` jeebs
2005-06-24 19:13 ` jeebs
2005-06-24 20:25 ` John R. Hogerhuis
2005-06-24 20:52 ` jeebs
2005-06-28 18:39 ` Jim C. Brown
2005-06-24 21:30 ` Tim Walker [this message]
2005-06-24 21:55 ` John R. Hogerhuis
2005-06-24 22:46 ` [Qemu-devel] " Ronald
2005-06-24 18:07 ` [Qemu-devel] " Christian MICHON
2005-06-21 10:42 ` [Qemu-devel] quick gtk2.c update Jernej Simončič
2005-06-21 12:36 ` Jim C. Brown
2005-06-21 16:30 ` jeebs
2005-06-21 17:25 ` Jernej Simončič
2005-06-21 10:39 ` Jernej Simončič
2005-06-21 10:32 ` Jernej Simončič
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=42BC7B80.2050803@astolat-it.co.uk \
--to=tim@astolat-it.co.uk \
--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).