glib/subprojects/zlib.wrap

[wrap-file]
directory = zlib-1.2.11
source_url = https://zlib.net/fossils/zlib-1.2.11.tar.gz
source_filename = zlib-1.2.11.tar.gz
source_hash = c3e5e9fdd5004dcb542feda5ee4f0ff0744628baf8ed2dd5d66f8ca1197cb1a1
patch_filename = zlib_1.2.11-6_patch.zip
patch_url = https://wrapdb.mesonbuild.com/v2/zlib_1.2.11-6/get_patch
patch_hash = f7c24c5698ce787294910ad431f94088102d35ddaf88542d04add1e54afa9212

[provide]
zlib = zlib_dep
meson: switch to the wrapdb wrap file for zlib As was suggested in #1405 Source: https://wrapdb.mesonbuild.com/zlib 2018-07-20 17:33:43 +02:00			`[wrap-file]`
			`directory = zlib-1.2.11`
			`source_url = https://zlib.net/fossils/zlib-1.2.11.tar.gz`
			`source_filename = zlib-1.2.11.tar.gz`
			`source_hash = c3e5e9fdd5004dcb542feda5ee4f0ff0744628baf8ed2dd5d66f8ca1197cb1a1`
Enable full-static build on Windows Glib cannot be built statically on Windows because glib, gobject and gio modules need to perform specific initialization when DLL are loaded and cleanup when unloaded. Those initializations and cleanups are performed using the DllMain function which is not called with static builds. Issue is known for a while and solutions were already proposed but never merged (see: https://gitlab.gnome.org/GNOME/glib/-/issues/692). Last patch is from version 2.36.x and since then the "constructor/destructor" mechanism has been implemented and used in other part of the system. This patch takes back the old idea and updates it to the last version of glib to allow static compilation on Windows. WARNING: because DllMain doesn't exist anymore in static compilation mode, there is no easy way of knowing when a Windows thread finishes. This patch implements a workaround for glib threads created by calling g_thread_new(), so all glib threads created through glib API will behave exactly the same way in static and dynamic compilation modes. Unfortunately, Windows threads created by using CreateThread() or _beginthread/ex() will not work with glib TLS functions. If users need absolutely to use a thread NOT created with glib API under Windows and in static compilation mode, they should not use glib functions within their thread or they may encounter memory leaks when the thread finishes. This should not be an issue as users should use exclusively the glib API to manipulate threads in order to be cross-platform compatible and this would be very unlikely and cumbersome that they may mix up Windows native threads API with glib one. Closes #692 2022-01-19 14:19:05 +01:00			`patch_filename = zlib_1.2.11-6_patch.zip`
			`patch_url = https://wrapdb.mesonbuild.com/v2/zlib_1.2.11-6/get_patch`
			`patch_hash = f7c24c5698ce787294910ad431f94088102d35ddaf88542d04add1e54afa9212`
meson: switch to the wrapdb wrap file for zlib As was suggested in #1405 Source: https://wrapdb.mesonbuild.com/zlib 2018-07-20 17:33:43 +02:00
Enable full-static build on Windows Glib cannot be built statically on Windows because glib, gobject and gio modules need to perform specific initialization when DLL are loaded and cleanup when unloaded. Those initializations and cleanups are performed using the DllMain function which is not called with static builds. Issue is known for a while and solutions were already proposed but never merged (see: https://gitlab.gnome.org/GNOME/glib/-/issues/692). Last patch is from version 2.36.x and since then the "constructor/destructor" mechanism has been implemented and used in other part of the system. This patch takes back the old idea and updates it to the last version of glib to allow static compilation on Windows. WARNING: because DllMain doesn't exist anymore in static compilation mode, there is no easy way of knowing when a Windows thread finishes. This patch implements a workaround for glib threads created by calling g_thread_new(), so all glib threads created through glib API will behave exactly the same way in static and dynamic compilation modes. Unfortunately, Windows threads created by using CreateThread() or _beginthread/ex() will not work with glib TLS functions. If users need absolutely to use a thread NOT created with glib API under Windows and in static compilation mode, they should not use glib functions within their thread or they may encounter memory leaks when the thread finishes. This should not be an issue as users should use exclusively the glib API to manipulate threads in order to be cross-platform compatible and this would be very unlikely and cumbersome that they may mix up Windows native threads API with glib one. Closes #692 2022-01-19 14:19:05 +01:00			`[provide]`
			`zlib = zlib_dep`