Re: What gives us the macro GSEAL()?

> So to protection is enable - must include gdkconfig.h.win32 in my
> aplications?

Eek, no. Include gdkconfig.h. Including the normal GTK+ headers
already does that for you.

When building GTK+ for Windows with MSVC, gdkconfig.h.win32 is copied
to gdkconfig.h.

If building GTK+ for Windows using mingw (either natively or
cross-building), the configure script creates gdkconfig.h.
gdkconfig.h.win32 is supposed to be effectively identical to the one
that the configure script produces (for the win32 backend case), to be
useable by people who build GTK+ with MSVC and thus have no POSIXish
environment to run the configure script in, that's the point with it.

> Now I don't see where gdkconfig.h.win32 include in GTK+ source

You don't believe this GSEAL thing is somehow Windows-specific, do you?


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