| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The reference counting of a DPAP record's thumbnail property was off.
This commit makes proper use of g_(byte)_array_ref. Libdmapsharing's
dmap-image-connection.c:_handle_mlcl() makes this necessary: it unrefs
the thumbnail pointer after passing it to g_object_set(record, ...).
Signed-off-by: W. Michael Petullo <mike@flyn.org>
|
|
|
|
|
| |
libdmapsharing4-devel is libsoup3 compatible while
libdmapsharing-devel is libsoup2 compatible.
|
|
|
|
|
|
|
|
|
|
| |
If we are on libsoup2 enviroment but with dmap enable,
meson will error out due a check in libdmapsharing4_dep:
src/dmap/meson.build:39:7: ERROR: Unknown variable "libdmapsharing4_dep". This patch fixes this error.
libdmapsharing4_dep is set only with libsoup3 but it only checks for
libdmapsharing-4.0, so we can do that always and fix the error.
|
| |
|
|
|
|
|
|
| |
The previous query was only searching in the metadatas of the media. So
if one doesn't have any metadata and we do a research by name, the results
was empty.
|
|
|
|
|
|
|
|
| |
Versions of libdmapsharing >= 3.9.11 (API 4.0) support libsoup
3.0. Building against libsoup 2.4 requires libdmapsharing's older 3.0 API,
which grilo-plugins will now select when building against libsoup 2.4.
Signed-off-by: W. Michael Petullo <mike@flyn.org>
|
| |
|
| |
|
|
|
|
| |
This will make it easier to support new pkg-config names and versions.
|
|
|
|
|
| |
It's needed for the gstreamer-1.0.pc pkg-config file used to gate
the chromaprint plugin being built.
|
|
|
|
|
|
| |
rest-devel isn't directly used by grilo or grilo-plugins, so don't
install it manually. If it is required by another library, it will pull
it in.
|
| |
|
|
|
|
|
|
|
|
| |
As libdmapsharing doesn't support libsoup3 yet.
Original patch by: Bastien Nocera <hadess@hadess.net>
See: #85
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The current check fails in multiple ways:
- the variable 'soupapiversion' needs to be checked in the pkg-config
file; using get_variable() will only check inside the dependency's
build system when used as a subproject
- grilo does not have a variable named 'soupapiversion' anyway; it's
called 'soup_api_version'
- this is far from being idiomatic Meson
We need to split the check into two:
- check for pkg-config variables when using a system dependency
- check for a variable in the internal dependency when using grilo as a
subproject
In order to make this work we are going to need the following MR in
Grilo:
https://gitlab.gnome.org/GNOME/grilo/-/merge_requests/95
|
|
|
| |
This reverts commit 8bcf29ed63c05257df3703bb91bdd6680a9ae850
|
|
|
|
|
|
| |
As libdmapsharing doesn't support libsoup3 yet.
Closes: #85
|
| |
|
|
|
|
|
|
|
|
|
|
| |
GNOME Online accounts removed flicker backend so we need to remove it
here too.
https://gitlab.gnome.org/GNOME/gnome-online-accounts/-/merge_requests/86
This basically reverts 2b973109 "flickr: use GOA to get user's
accounts"
|
|
|
|
|
|
|
|
|
|
|
|
| |
When we need to request the config, the request's callback will flush
out the queue of requests. So, when we need the config, be sure to
only run_pending_requests with max_num_request set to 1.
Also, to avoid reuse of the same GrlTmdbRequest, I've added a warning
to its grl_tmdb_request_run_async().
Found this after switching internals of GrlNetWc to use GTask instead
of GSimpleAsyncResult.
|
|
|
|
| |
Signed-off-by: Victor Toso <victortoso@gnome.org>
|
| |
|
| |
|
|
|
|
|
|
|
| |
Since libgdata 0.17.0 and the switch to the YouTube v3 API, all feed
types except GDATA_YOUTUBE_MOST_POPULAR_FEED have been deprecated.
See the gdata_youtube_service_query_standard_feed() API documentation.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Remove libsoup dependency and bump glib dependency to 2.66 so we can use
GUri instead of SoupURI.
|
| |
|
|
|
|
|
|
| |
As libgdata isn't ported to libsoup3 yet.
See https://gitlab.gnome.org/GNOME/libgdata/-/merge_requests/28
|
| |
|
|
|
|
| |
It was removed in 2ce6c6e90f631357b6204bd10803f8641cb25db4.
|
|
|
|
| |
It was removed in d6d91c7cf27de78b0b0575daeeddb1ae7f69cc94.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|