| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
GLib is discussing deprecating/removing it upstream [1] since it has
only limited uses. Next to that, it seems to bork stack traces here when
using ASAN (for which you also have to specify `G_SLICE=always-malloc`
too).
In other words, let's just get rid of using `GSLice` and call the
allocation APIs directly.
[1]: https://gitlab.gnome.org/GNOME/glib/-/issues/1079
|
|
|
|
|
|
|
|
|
|
| |
When build with meson, the GCK version macros went from indicating version
3.34.0 down to version 1.0.0, presumably accidentally. This is not great as
it makes GCK_CHECK_VERSION() entirely useless.
Let's make sure the newer version have higher version numbers again.
Fixes: a705acc3640e ('Support Meson build system')
|
|
|
|
|
|
|
|
|
|
| |
gck provided some APIs that made working with lists of `GObject`s
easier. GLib has for a long time added API that works well enough for
the same use case, like `g_list_copy_deep()`, `g_list_free_full()` and
more recently also `g_clear_list()`, so use those instead.
This commit also bumps the required GLib version to a more modern 2.64
(which is needed for the `g_clear_list()` API).
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
It's a Vala-specific thing, and since the header file is coming from
p11-kit (see also the previous commit), there's always a chance we ship
an outdated version.
Projects that were relying on the VAPI file should probably have their
own copy, or someone should put it in vala-extra-vapis.
|
|
|
|
|
| |
Stop shipping our own copy now that we're doing a version bump (see also
https://bugzilla.gnome.org/show_bug.cgi?id=680271)
|
| |
|
|
|
|
| |
They're unused and outdated.
|
| |
|
|
|
|
| |
Do not mismatch them.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Set the GMutex directly in the structure.
|
| |
|
|
|
|
|
|
|
| |
It is not necessary and makes it difficult to interact with GObject introspected
languages.
Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
|
|
|
|
| |
Automatically define the error quark with this macro.
|
| |
|
|
|
|
| |
Also remove the compatibility test and objects.
|
|
|
|
| |
Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
|
|
|
|
|
|
|
| |
This means that GckObjectCacheIface becomes GckObjectCacheInterface and
GCK_OBJECT_CACHE_GET_INTERFACE becomes GCK_OBJECT_CACHE_GET_IFACE.
Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
|
| |
|
|
|
|
|
|
| |
Do not rely on major_version to manually create the library names.
Make sure to be consistent and use a single variable for all the library names
and folder mentions.
|
|
|
|
|
|
|
|
|
|
|
|
| |
This argument has been removed in Meson 0.61.0:
gck/meson.build:130:2: ERROR: gnome.generate_gir got unknown keyword arguments "packages"
https://github.com/mesonbuild/meson/commit/f8fc5cb860465718fe7c79a1bf1fe00659f138de:
> The packages argument to gnome.generate_gir was allowed, but never did anything, so stop passing it.
Fixes #89
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
gtk-doc has been slowly dying for the past few years. With gi-docgen we
have a clear successor in sight to replace the voodoo magic one needs to
get the whole documentation setup.
See the [gi-docgen tutorial] for more info on how the system works.
Since we're now only the C compiler (and GIR) parse the C code, that
means we can also get rid of all the special escapes for the # character
in PKCS#11.
[gi-docgen tutorial]: https://gnome.pages.gitlab.gnome.org/gi-docgen/tutorial.html
|
|
|
|
|
|
|
| |
This fixes a few (fatal in gcc 11) warnings, breaking the CI.
For the original discussion on why this change is needed, see
https://gitlab.gnome.org/GNOME/glib/-/issues/600
|
|
|
|
|
| |
Never return or expect arguments as paramter for gck_call_* functions,
instead use gck_call_get_arguments to interact with them when needed
|
|
|
|
|
| |
This is to mimic GTask more and so we can avoid using a temporary task
only for temporary storing an object pointer.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GckCall uses its own implementation of threads pool to handle the async
calls, now that we've GTask this code can be simplified by reusing
GLib code.
I didn't want to change the API in this commit, even if private not to
mix changes together, so the functions still are used as they used to be
The main difference is that the async_pre and async_ready prepare a
GTask instance, while the async_go starts a thread using the gtask
function.
Callback functions needed to be adapted to the new GAsyncResult type.
Tests needed also some tuning as the underneath task holding a reference
to the source object might be finalized at later stage, when the
thread-related data is removed, as per this we may wait a bit to check
whether a source object gets finalized, this is due to GNOME/GLib#1346.
|
|
|
|
|
| |
We have a modern, saner build system in place with Meson, so let's drop
autotools before releasing the next version of gcr.
|
|
|
|
|
|
|
| |
`g_assert()` can be (accidentally) disabled if someone uses
`G_DISABLE_ASSERT` when compiling gcr, so that renders most tests
useless. As a nice side effect, we get better error report when
something goes wrong in a test.
|
| |
|
|
|
|
| |
`GSimpleAsyncResult` is deprecated in favor of `GTask`.
|
|
|
|
|
| |
Given that gck_slot_has_flags changed meaning in the previous commit,
add back a function that allows to get the slot token flags
|
|
|
|
|
| |
The function is meant (by name and documentation) to check the slot info
flags, but instead it gets and checks the token tags.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
If the format string for strptime() doesn't include a time zone,
then the tm_isdst member will be left uninitialized (see NOTES in
Linux strptime(3)). This means we will be off by an hour from the
intended time if whatever arbitrary junk is on the stack happens to
include a positive value for tm.tm_isdst.
Resolves: https://gitlab.gnome.org/GNOME/gcr/issues/42
Bug-Debian: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=953981
Signed-off-by: Simon McVittie <smcv@debian.org>
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make more use of g_assert_cmpint and friends so that the error message
indicates more clearly what we were expecting and what we got.
This also has the minor benefit that unlike g_assert(), the more
test-oriented macros aren't disabled by G_DISABLE_ASSERT, so we don't
need to worry about whether we are relying on their side-effects.
Helps: #42
Signed-off-by: Simon McVittie <smcv@debian.org>
|
| |
|
|
|
|
|
|
|
| |
If we want applications to switch, deprecation warnings are a good way
to make that happen.
Fixes https://gitlab.gnome.org/GNOME/gcr/issues/36
|
| |
|
|
|
|
|
|
| |
We needed this for the call to `strptime()` and `timegm()`.
Also once we missed a `#include <time.h>`
|
|
|
|
|
|
| |
Meson isn't setting the "Requires" field, so we have to do it manually.
Since we don't want to specify each dependency in `glib_deps` as a
dependency, we also give each a separate variable.
|
|
|
|
|
|
| |
This prevents some unnecessary string copies, resulting in less memory
used and some unnecessary performance overhead being removed. Well, a
little bit at least.
|