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: Holger
Subject: Re: [Bug-gnubg] GTK+ 2.2 Win32 build: display much too slow
Date: Thu, 23 Jan 2003 21:37:02 +0100

On Wed, 22 Jan 2003 23:58:01 +0100, "Nardy Pillards"
<address@hidden> wrote:
>From: "Holger" <address@hidden>
>> On Wed, 22 Jan 2003 18:05:32 +0100, "Nardy Pillards"
>> <address@hidden> wrote:
>> >> 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.

Hmm, I'm not sure whether this is safe. Maybe it worked this time. But
if the headers changed from 2.0 to 2.2 (I think they did?) you might
have trouble hunting the bug another time.

>> 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 didn't succeed so far. Could you tell me with what options you ran
configure?

>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.

At least at university I don't have problems with bandwidth. :-)

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

Does it do any special checks on Windows? I suppose it would need to.

Regards,

        Holger




reply via email to

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