Re: GTK2 GdkNativeWindow compilation errors

Also, is there a specific version you are patching against? 8.0, 8.1, or 9.=
0?







On Thursday, April 17, 2025 at 04:46:30 PM EDT, Lance Dillon <riffraff169@y=
ahoo.com> wrote:=20





Is this a compile time error, or a runtime error?=C2=A0 If runtime, is ther=
e example code you have that seems to trigger it?






On Thursday, April 17, 2025 at 04:05:16 PM EDT, H. William Welliver <willia=
[email protected]> wrote:=20





Hi Lance-

Thanks for the assistance. I=E2=80=99ve attached the patch to this message,=
 it should detect the presence of GdkNativeWindow. Let me know how it works=
 for you (and the result of that test in the configure output).




> On Apr 17, 2025, at 3:26=E2=80=AFPM, Lance Dillon <[email protected]>=
 wrote:
>=20
> I could test
>=20
> Yahoo Mail: Search, Organize, Conquer
>=20
>=20
>>=C2=A0=C2=A0
>>=C2=A0=C2=A0
>> On Thu, Apr 17, 2025 at 15:18, H. William Welliver
>> <[email protected]> wrote:
>>=20
>>=20
>>=C2=A0=C2=A0
>> I compiled pike on a system that has a version of GTK2 that includes a t=
ypedef for GdkNativeWindow that the GTK2 code doesn=E2=80=99t specifically =
address. The compiler (a recent clang) errors on these implicit casts to an=
d from GdkNativeWindow (which I believe resolves to a platform dependent po=
inter) and integers that the pike glue deals with. I was able to solve the =
errors but wanted to get some feedback before I commit it, as I get the imp=
ression that GdkNativeWindow was something added somewhere along the way, s=
o there probably may need to be some configure glue added. Is anyone using =
the GTK2 module that might be able to test these changes to see if they cau=
se problems elsewhere? Or should I commit a best-guess fix and wait to see =
how pikefarm reacts?
>>=20
>> Bill
>>=20
>>=20