bug-gnubg
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Bug-gnubg] GTK+ 2.2 Win32 build: display much too slow


From: Nardy Pillards
Subject: Re: [Bug-gnubg] GTK+ 2.2 Win32 build: display much too slow
Date: Wed, 22 Jan 2003 23:58:01 +0100

From: "Holger" <address@hidden>
Sent: Wednesday, January 22, 2003 6:33 PM
> On Wed, 22 Jan 2003 18:05:32 +0100, "Nardy Pillards"
> <address@hidden> wrote:
> >> From: "Gary Wong" <address@hidden>
> >> Sent: Tuesday, January 21, 2003 9:43 PM
> >> [snip]
> >>
> >> > If this program is also slow, GTK+ itself appears to be the problem.
I
> >> > find it hard to believe that it would be released in this state.
> [snip]
> >> I took old pango-basic-win32
> >> Gtkspeedtest: 2 secs now
> [snip]
> >With the 'old' pango-basic-win32.dll (v. 1.0.2.2 2002/05/25) in stead of
the
> >current one (v. 1.0.5.10),
> >GNUBg build with GTK+2.2 runs smoothly.
> >Still a bit slower, but these delays are reasonable.
>
> Did you only exchange the DLL or also the corresponding headers?

I only changed the pango-basic-win32.dll (20 KB), nothing else.

> And could you be so kind to send me your config and make-files again
> for GTK+ 2.2? I had a few problems with undefined references while
> linking (mostly g_type_check_instance_cast, g_type_check_instance_cast
> and a few others).

Doing it with MSYS and ./configure.
So I could send you my makefile and config.h, but there are some pointers to
MSYS, and some to MinGW, and it is meant to be made automatically.
And there needs to be done some more work.

I think though is good idea to put makefile and config.h 'the old way' for
the branch (with GTK+2.2 GUI)
and MSYS / MinGW for the trunk.
MSYS/MinGW: big downloads, frequent updates (of components)... so even an
advanced user would still need a fast internet connection to keep up.

Oh... BTW: ./configure does not give a #define WIN32 1 and either
the -lwinmm lib.

If all this sounds foolish... please tell. I'm used to be called 'silly'.

Nardy


> Regards,
>
> Holger
>





reply via email to

[Prev in Thread] Current Thread [Next in Thread]