Disable GIO modules without provoking scary warnings (#32)
- Oct 22, 2020
-
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This lets them access non-public API, and means there's one less thing that can go wrong. The cost is about 500K, which is much smaller than a Steam Runtime. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
The code under test was already moved, but the tests couldn't follow until their executable was statically linked to libsteam-runtime-tools, which it now is. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
We no longer need to, because the test is now linked statically. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
This test exercises internal functions that shouldn't really be visible in the ABI. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-
Simon McVittie authored
Now that GIO_MODULE_DIR has been backported into scout's GLib, we can disable GIO modules completely, instead of loading them but then not using them. This avoids some misleading warnings (#32). This will not be completely effective on non-Debian systems until we also patch scout's GLib to make GIO_MODULE_DIR take precedence over the hard-coded legacy search path /usr/lib/gio/modules. The unit test for this is still in tests/pressure-vessel/utils.c for now. Signed-off-by:
Simon McVittie <smcv@collabora.com>
-