luc14n0/glib
1
0
Fork 0
mirror of https://gitlab.gnome.org/GNOME/glib.git synced 2025-02-05 10:38:08 +01:00
Code Issues Packages Projects Releases Wiki Activity
glib/gio/tests/modules/symbol-visibility.h

21 lines
639 B
C
Raw Normal View History

meson: Add tls-interaction test, and fix giomodule test giomodule test needed symbol visibility pragmas added. This is needed on Windows anyway, so it's better to do it this way rather than disabling -fvisibility=hidden for the test modules.
2016-12-21 07:46:30 +05:30
#ifndef GLIB_TEST_SYMBOL_VISIBILITY
#define GLIB_TEST_SYMBOL_VISIBILITY
/* This is the same check that's done in configure to create config.h */
#ifdef _WIN32
giomodules: g_io_module_* must always be exported Those symbols are not used by GIO itself but by external modules.
2022-10-05 17:40:57 -04:00
#ifdef GLIB_TEST_STATIC_COMPILATION
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
#define GLIB_TEST_EXPORT_SYMBOL extern
#else
#ifdef _MSC_VER
#define GLIB_TEST_EXPORT_SYMBOL __declspec(dllexport) extern
#else
#define GLIB_TEST_EXPORT_SYMBOL __attribute__ ((visibility ("default"))) __declspec(dllexport) extern
#endif
#endif
meson: Add tls-interaction test, and fix giomodule test giomodule test needed symbol visibility pragmas added. This is needed on Windows anyway, so it's better to do it this way rather than disabling -fvisibility=hidden for the test modules.
2016-12-21 07:46:30 +05:30
/* Matches GCC and Clang */
#elif defined(__GNUC__) && (__GNUC__ >= 4)
# define GLIB_TEST_EXPORT_SYMBOL __attribute__((visibility("default"))) extern
#endif
#endif /* GLIB_TEST_SYMBOL_VISIBILITY */
Reference in New Issue Copy Permalink