[EMAIL PROTECTED] wrote:
> Putting more stuff into the common files folders is just going to be
> 'clutter'.
>
> Things will never get used by any other application. Eventually the user
> will even entirely forget they are there.
>
> It just ends up being clutter.
Heya Jeebs,
There are nu
"Jim C. Brown"
> I must disagree here. If a user already has xchat 2 installed, and that
> person
> wants to try to use qemu with the GTK interface, they already have the
> libraries
> that they need.
>
> Including a set of GTK libraries just for qemu would not only be redundant
> in
> this cas
On Tue, Jun 21, 2005 at 05:45:12PM -0500, [EMAIL PROTECTED] wrote:
> "Jim C. Brown"
> > I disagree. I think distributing the GTK library with qemu (even for
> > windows
> > versions) is a very bad idea. At most, the qemu installer should just
> > download
> > and run the GTK installer. At most.
>
On Tue, Jun 21, 2005 at 05:45:12PM -0500, [EMAIL PROTECTED] wrote:
> > GTK libraries are not part of qemu, they are a separate resource that qemu
> > depends on.
>
> As far as the user is concerned, they are part of qemu.
>
I must disagree here. If a user already has xchat 2 installed, and that
"Jim C. Brown"
> I disagree. I think distributing the GTK library with qemu (even for
> windows
> versions) is a very bad idea. At most, the qemu installer should just
> download
> and run the GTK installer. At most.
It's a very bad idea to have the installer need to go back on to the net to
do
On Tue, Jun 21, 2005 at 04:19:33PM -0500, [EMAIL PROTECTED] wrote:
> >I'd say it's worth it, if Qemu gains a usable GUI this way. GTK+ libraries
> >are ~3,5MB download, and only need to be installed once.
>
> Putting libraries like this in a common location is always a bad thing.
> That means the
> Not a lot yet. I have a minimal ftp server that would be perfect to use
> with qemu, with much of the code rewritten. However, to make it interface
> with slirp a lot more work is needed (basicly the ftp server uses sockets
> while slirp works with tcp/ip packets directly. Thus I have to write a
On Tue, Jun 21, 2005 at 02:40:26PM -0500, [EMAIL PROTECTED] wrote:
> >export CFLAGS="$CFLAGS -mms-bitfields"
>
> Okay, I tried that.
>
> I then did a 'make clean'. Then the config, then the regular make
>
> But running the resulting qemu is still giving the same error.
>
>
Not the slightest
On Tue, Jun 21, 2005 at 10:39:14PM +0100, Paul Brook wrote:
>
> > Not a lot yet. I have a minimal ftp server that would be perfect to use
> > with qemu, with much of the code rewritten. However, to make it interface
> > with slirp a lot more work is needed (basicly the ftp server uses sockets
> >
"Jernej Simonèiè"
>Hmm, it's been a while since I last tried compiling Qemu, but maybe you'll
>need to edit the makefiles to actually include that flag.
That's what I did. He sent me the patch to do that.
It runs, but there are keyboard problems.
>> The gtk libraries are more than 6 meg and w
I keep getting this with the standard file.
[EMAIL PROTECTED] [ ~/qemu-0.7.0/] 138> sh configure
configure: bad substitution
[EMAIL PROTECTED] [ ~/qemu-0.7.0/] 139>
When I take out the bsd magic since I only care about SVR4, I get a
bunch of compile time errors.
Any suggestions? Should I be
On Tuesday, June 21, 2005, 21:40:26, [EMAIL PROTECTED] wrote:
>>export CFLAGS="$CFLAGS -mms-bitfields"
> Okay, I tried that.
> I then did a 'make clean'. Then the config, then the regular make
> But running the resulting qemu is still giving the same error.
Hmm, it's been a while since I last
On Tue, Jun 21, 2005 at 04:17:08PM +0200, Jan Marten Simons wrote:
> Jim C. Brown wrote:
>
> >I've been convinced. I'll take a look at it and see what can be done for a
> >builtin ftp server.
> >
> Hi Jim,
>
>
> Are there any results, yet?
> I'd like to help with testing this feature, as I canno
How difficult would it be to create a (presumably Linux) uniform build
environment for all targets as a bootable Qemu image?
___
Qemu-devel mailing list
Qemu-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/qemu-devel
"Jernej Simonèiè" <[EMAIL PROTECTED]>
>> The unzip into the proper mingw directory structure.
>Did you unzip to /mingw or to /? If the latter, you'll probably have
Into the mingw directory.
That part seems to compile etc. It's the resulting program that is screwed
up some how.
>export CFLAG
On Tue, Jun 21, 2005 at 11:27:10AM -0500, [EMAIL PROTECTED] wrote:
> I downloaded the libraries and devel files from the link Jernej Simoncic
> recommended. It does seem to be a main win gtk distrib location. (As
> somebody pointed out, actually building gtk etc. under Mingw is a pita. I
> ha
$B!I!y!I!I!y!I!I!y!I(B
$B5U1g$O"-(B
http://www.awg4.com/ss/?lip1
$BITNQ"-(B
http://www.awg4.com/ss/?lip2
$B5U6L!&6L$NMA$O"-(B
http://www.awg4.com/ss/?lip3
$B(-40(-A4(-L5(-NA(-%](-%$(-%s(-%H(-$G(-(B
$B(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(,(0(B
$B(-AG(-?M(-=w([EMAIL PROTECTED](-$r(-%2(-
On Tuesday, June 21, 2005, 18:30:07, [EMAIL PROTECTED] wrote:
>>Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and
>>compiling
>>any GTK+ program on Windows - the libraries are always built to be
>>compatible with MSVC so that you can use 1 set of libraries for all
>>programs.
> I
On Tuesday, June 21, 2005, 18:27:10, [EMAIL PROTECTED] wrote:
> I downloaded the libraries and devel files from the link Jernej Simoncic
> recommended. It does seem to be a main win gtk distrib location. (As
> somebody pointed out, actually building gtk etc. under Mingw is a pita. I
> haven't
> This is a particularly perplexing error, considering that a) this error
> should
> only show up if you 1) use a MSVC compiled GTK with a mingw/cygwin
> compiled
I downloaded the libraries and devel files from the link Jernej Simoncic
recommended. It does seem to be a main win gtk distrib loc
From: "Jernej Simonèiè"
>> No idea what it really means. Other than what it actually says.
>Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and
>compiling
>any GTK+ program on Windows - the libraries are always built to be
>compatible with MSVC so that you can use 1 set of librar
Jim C. Brown wrote:
>I've been convinced. I'll take a look at it and see what can be done for a
>builtin ftp server.
>
Hi Jim,
Are there any results, yet?
I'd like to help with testing this feature, as I cannot really help with
coding.
Jan
___
Qemu
On Tue, Jun 21, 2005 at 12:42:56PM +0200, Jernej Simon?i? wrote:
> On Tuesday, June 21, 2005, 4:58:06, [EMAIL PROTECTED] wrote:
>
> > No idea what it really means. Other than what it actually says.
>
> Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and compiling
> any GTK+ progra
On Tuesday, June 21, 2005, 4:58:06, [EMAIL PROTECTED] wrote:
> No idea what it really means. Other than what it actually says.
Do a export CFLAGS="$CFLAGS -mms-bitfields" before configuring and compiling
any GTK+ program on Windows - the libraries are always built to be
compatible with MSVC so t
On Tuesday, June 21, 2005, 6:28:44, Jim C. Brown wrote:
> This is a particularly perplexing error, considering that a) this error should
> only show up if you 1) use a MSVC compiled GTK with a mingw/cygwin compiled
> app or 2) use a mingw/cygwin compiled GTK with a MSVC compiled app. Since you
> u
On Tuesday, June 21, 2005, 4:27:04, [EMAIL PROTECTED] wrote:
> I'd rather keep them in the qemu directory. Just like I do with sdl.dll
Semi-official place to put GTK+ libraries on Windows is C:\Program
Files\Common Files\GTK\2.0, and then adding bin\ subdirectory to PATH. This
is what GTK+ insta
On Monday, June 20, 2005, 3:59:11, Jim C. Brown wrote:
> I did find a GTK Windows tutorial at
> http://wolfpack.twu.net/docs/gtkwin32/,
> but that says to install the dlls to the System folder.
Thanks to people like that I had to put detection of such broken installs to
the GTK+ installer distrib
Hi,
I just installed WinNT 3.51 & 4.0 WKS to a PREP machine(Power Series
Thinkpad). The first thing I had to do was installing ARC disk image to
PREP 0x41 partition on HD. This Arc utility is then used for
partitioning HD(Winnt PPC cant do this). And Winnt setup has to be
launched from ARC
Hi all,
I've made a patch for OS X to use the built-in CD-ROM drive. (-cdrom
/dev/cdrom).
I used #ifdef COCOA_CONFIG in block.c and added -framework
CoreFoundation -framework IOKit to COCOA_LIBS in makefile.target.
This works ok.
But I want the Patch to work with SDL, too.
So I use #ifdef __
29 matches
Mail list logo
