-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 04/20/2016 02:18 PM, Mart Raudsepp wrote: > Ühel kenal päeval, N, 21.04.2016 kell 06:53, kirjutas Kent > Fredric: >> On 21 April 2016 at 06:38, Ian Stakenvicius <[email protected]> >> wrote: >>> Well so far the only needs I have run into for the win32 flag >>> has been in relation to choosing UI toolkit support for cairo >>> and gtk+ (and possibly others in the future), which is why I >>> saw the parallel. >> >> >> Given you're not using the flag to indicate "works on win32" as >> such, but instead "compile using Win32 Widgets instead of >> something else", wouldn't a better name indicate that somehow? >> >> The simplest thing I can think of that clears this confusion is >> a few extra characters: >> >> "win32gui", "win32ui" >> >> Or something along those lines. >> >> It doesn't require us to know what the exact binding keywords in >> microsoft terminology is used, and it clearly communicates >> "This is something to do with User Interfaces" as opposed to >> "Just linking/compiling slightly differently". > > win32 is what the base API seems to be called all over in the wild. > The GTK+ configure flag is also --enable-win32-backend in gtk3 and > --with-backend=win32 in gtk2 (didn't personally check the latter). > Note that gtk configure actually also tracks platform_win32 and > os_win32 in there, which are different things (and just > configure.ac internal names). Former is true when host contains > mingw, latter when host contains mingw or cygwin. When win32 gdk > backend is enabled (which the propose USE flag would do), then it > will depend on a matching cairo backend of that, to be able to do > its own drawing on Windows. There's actually some stuff about > pangowin32 as well, not sure Ian has noticed that yet. > > The GDK win32 backend uses what is called the win32 API. See e.g > https://en.wikipedia.org/wiki/Windows_API#Versions For example a > GdkWindow is created via CreateWindowExW, root of that > documentation is apparently at > https://msdn.microsoft.com/en-us/library/windows/desktop/ff818516(v=vs.8 5).aspx > > It doesn't use the Windows API higher level UI stuff, like > wxWidgets does, but only the low-level stuff, and then emulating > the themeing as best as it can right now, like Qt does. So in that > way win32gui might be misleading. win32 or win32api or winapi or I > dunno. > > Theoretically you can also build this stuff for consumption with > wine. Or maybe ReactOS? Basically the only real point I have is > that anything kernel_* to control this probably doesn't make > sense. Wine's dlls and programs (notepad/winemine/etc.) can be cross compiled using mingw. It's mostly only useful for testing purposes (e.g., verifying that a certain wine dll also breaks an application the same way on windows to confirm where the problem lies). I used to build them regularly and upload to sourceforge, but haven't in a while, as it seems there's little interest. In addition, wine does use mingw if available for cross compiling its test suite, but most users don't need/want that. - -Austin -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJXF9kJAAoJEACzKVe5S/Ph+JIP/3l/spsw9AuanEbmKsYVIjg3 ErBs0omQ191mAPpovJWH0qejJaTAzneNbhXNIne8AE00L745rxensj4vtEunL9YU QZ//nBNr2jGxX/SKmZqYn7A7+kgW9qXOVvYFWQebbyXy/DxhzMoTtP02Lvd/THyW 20W9kBS766/iuW6x6/qRRptbENMs2t3aR1B+JjB8OH/e/eAzU4RfnwuWI36D227S 56MgzuVbaY1ON+su9n/WhqjEdPitj9WaUDyxDNgglPfAcn6yVvlbXgN8CjsGo0cf TleJhc2Kw0AYvt9V68D5oSt9l66ndC1/Zoy3r2fsboioCwqhhYI5SHWTC290iRc+ KbXOZJiCUIDahZ6YgiktkwmpODG9vb6hc9qVB7gKvX9gMZa6d9BFLxbs7lsvJ7eG W/5ShV998tDSd63g1iKPtlyichUMQPCm5cmTVt4M3d0L19qadq4AKPr5Ap8N7dPC YPpm8+m2FnC2iV4fFot7MTQSoJEmvWhXG8P50M/bKXyyzqRQqp+ntTE13hGILAsk oeTdCJ/QyJrCMgJdhtjKXHcWcpAXjD0j3LbL8pRgVLiR7JtKoWOCEXvTzQRVixEz rddxj+US3PUOFaEOLuJro7mNHHhUQanISeNQV2hOop0vBYdW9I8mL0UkfRWyjxR7 DPsjXwQYODQoJl1uWt/j =MRRF -----END PGP SIGNATURE-----
