From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1DnLT9-00082p-KT for qemu-devel@nongnu.org; Tue, 28 Jun 2005 15:10:03 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1DnLM6-0006DO-Qx for qemu-devel@nongnu.org; Tue, 28 Jun 2005 15:02:53 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1DnLLz-00061L-Si for qemu-devel@nongnu.org; Tue, 28 Jun 2005 15:02:39 -0400 Received: from [128.8.10.162] (helo=po0.wam.umd.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1DnL4I-0005Ol-LX for qemu-devel@nongnu.org; Tue, 28 Jun 2005 14:44:22 -0400 Received: from jbrown.mylinuxbox.org (jma-box.student.umd.edu [129.2.237.180]) by po0.wam.umd.edu (8.12.10/8.12.10) with ESMTP id j5SIdgjh018509 for ; Tue, 28 Jun 2005 14:39:42 -0400 (EDT) Date: Tue, 28 Jun 2005 14:39:25 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Build environment image Message-ID: <20050628183925.GA22295@jbrown.mylinuxbox.org> References: <1119644713.766.9.camel@aragorn> <001c01c578ff$21884720$334d21d1@organiza3bfb0e> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <001c01c578ff$21884720$334d21d1@organiza3bfb0e> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Fri, Jun 24, 2005 at 03:52:20PM -0500, jeebs@yango.us wrote: > "John R. Hogerhuis" > > > > > I can't say. But even if it were, I'd guess most here would rather work > > under Unix-like OS. > > Undoubtably. > > The Linux builders outnumber the Win builders by probably 50 to one. If not > more. > I just installed cygwin in my Windows XP inside of qemu. Ah, home away from home .. at home. Anyways, this might make for an interesting testing server. > But I know from the effort I went through to get qemu to build under windows > that it can indeed be a problem. > > And it's a bit sensitive to what other stuff you may install. And which > version of Mingw you do. (Older works, newer doesn't.) > What about cygwin with -mno-cygwin? > And a library header was in a different location than expected. > I didn't have an actual Windows GTK installation to look at, so I was just guessing. If I had a properly set up cross compile environment, that probably wouldn't have happened. Of course, we'd have to get it right first, but that only has to be done once. > Well, when I was building the gtk version for Jim, we did encounter a > situation with the libraries. > > His build didn't use the same settings as the prebuilt ones did for Windows. > > A linux environment might be inclined to just build the whole thing. And to > use paths as located in linux. > > It's also possible that developers may introduce more linux specific stuff > without even realizing it. > > I'm just saying that some Win build issues might show up that you didn't > think about while doing a Linux one. > The main issue is a testing environment. E.g. a way to run the compiled code once the build completes to make sure everything works. -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.