| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
| |
It is not necessary and makes it difficult to interact with GObject introspected
languages.
Signed-off-by: Corentin Noël <corentin.noel@collabora.com>
|
| |
|
|
| |
Also remove the compatibility test and objects.
|
| |
|
|
|
|
|
| |
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>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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.
|
| |
|
|
|
|
|
| |
`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.
|
| | |
|
| |
|
|
|
|
| |
Since we want to use this from the gcr/ code
https://bugzilla.gnome.org/show_bug.cgi?id=735873
|
| |
|
|
|
| |
We want to use 2.38.x and 2.36.x APIs in the GcrSshAskpass code
and the 2.38.x has been available in most distributions for a while.
|
|
|
gtk-doc doesn't work as an included Makefile so continue to
use SUBDIRS with docs/reference/*
Run the tests using TAP. Unfortunately the GTest --tap output
mode doesn't behave well in the face of failures, and doesn't
output a test plan. Use our own tap-driver and tap-compiler
for these reasons.
This also fixes several builddir != srcdir issues and testing hacks
that were sneaking around in the code base.
Move the tests into the same directories as the code that it
is testing.
|
