| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
These are hopefully complete already. I have compared an Autotools-built
and a Meson-built install of libmediaart and found only the following
differences:
* libmediaart-2.0.la isn't generated by Meson
* External references in the gtk-doc documentation are relative with
Meson and absolute with Autotools
* Some changes in generated .vapi file and .pc file
https://bugzilla.gnome.org/show_bug.cgi?id=783562
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously we relied on libtool's -export-symbols-regex feature, but we
are hoping to drop GNU Autotools and GNU Libtool in soon in favour of
Meson.
Meson doesn't have an equivalent feature, instead the advice is to
control symbol visibility at compile time.
The approach taken in this patch is based on Pango's build system. Pango
tells the compiler to hide symbols by default (if possible), and then defines
a _PANGO_EXTERN variable at compile time which marks a single symbol as
public. In Pango's case there is then further machinary to hide symbols
based on deprecation policies but I have not copied that here, instead I
used _LIBMEDIAART_EXTERN directly.
If a compiler doesn't support hiding symbols then the library we build
makes all symbols available, which is exactly what would happen before
on platforms where the libtool didn't have an implementation for
-export-symbols-regex.
See also:
http://mesonbuild.com/FAQ.html#how-do-i-do-the-equivalent-of-libtools-exportsymbol-and-exportregex
https://git.gnome.org/browse/pango/
https://git.gnome.org/browse/pango/tree/pango/pango-version-macros.h
https://gcc.gnu.org/wiki/Visibility
https://gcc.gnu.org/onlinedocs/gcc/Code-Gen-Options.html#Code-Gen-Options (-fvisibility)
|
|
|
|
|
|
|
|
| |
This flag was just enabling a codepath that sets QT_QPA_PLATFORM=minimal
in the environment before constructing a QCoreApplication instance.
This code path has no effect anyway: QT_QPA_PLATFORM only has an effect
if you are using QGuiApplication.
|
|
|
|
|
|
| |
Fixes this warning:
libmediaart/extract.h:93: Warning: MediaArt: multiple comment blocks documenting 'media_art_error_quark:' identifier (already seen at extract.c:1279).
|
|
|
|
|
| |
We need those files to be generated before the library is built, but it
seems Automake is failing miserably in conditions of massive parallelism.
|
|
|
|
|
|
|
|
|
| |
Under massive parallelism — like the Continuous build — we may end up in
a situation where the sources get built before the marshaller sources
are generated.
Let's try to increase chances that the dependency tracking inside
Automake will do the right thing.
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=767959
|
| |
|
|
|
|
| |
Otherwise the function is unusable through gobject-introspection.
|
|
|
|
|
| |
There are paths where the stop variable is not set, so might
end up with an uninitialized value when checked.
|
| |
|
|
|
|
|
| |
Adds optional configure flag "--with-qt-version=<4|5>" that may be used to
enforce qt 4.x or qt 5.x version.
|
|
|
|
|
| |
Use -export-symbols-regex to hide private symbols which should not be
exported.
|
|
|
|
|
|
|
| |
Documentation says "or NULL" and the code also handles it, but the g-i
for this was missing.
https://bugzilla.gnome.org/show_bug.cgi?id=739943
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=739942
|
|
|
|
|
|
|
| |
debug was printing g_strerror(errno) even in success case, leaving
weird confusing messages, indicating an error even if symlinking succeeded.
https://bugzilla.gnome.org/show_bug.cgi?id=739873
|
|
|
|
| |
Otherwise subprocess tests that assert by design leave those behind
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
This is deemed quite useless now and we should not be littering the file
system with .mediaartlocal directories everywhere.
https://bugzilla.gnome.org/show_bug.cgi?id=722795
|
|/
|
|
|
|
|
|
| |
Part of this API changes makes the media_art_get_{path|file}() APIs not do
i/o operations like creating the cache directory. This is now done in
media_art_process_new().
https://bugzilla.gnome.org/show_bug.cgi?id=724879
|
|\ |
|
| |
| |
| |
| | |
https://bugzilla.gnome.org/show_bug.cgi?id=724879
|
| | |
|
|/
|
|
|
|
|
|
| |
Part of this API changes makes the media_art_get_{path|file}() APIs not do
i/o operations like creating the cache directory. This is now done in
media_art_process_new().
https://bugzilla.gnome.org/show_bug.cgi?id=724879
|
| |
|
| |
|
|
|
|
|
|
|
|
|
| |
The function media_art_get_file checks for null values in artist, title and
prefix arguments, and puts special values on them if they do.
Do the same on media_art_get_path which calls media_art_get_file internally.
https://bugzilla.gnome.org/show_bug.cgi?id=727478
|
|
|
|
| |
https://bugzilla.gnome.org/show_bug.cgi?id=731681
|
| |
|
| |
|
|
|
|
| |
AutoMake warning += vs = for EXTRA_DIST/CLEANFILES
|
|
|
|
|
|
|
| |
Also added some checks into the API and a return value to know if the function
was successful.
https://bugzilla.gnome.org/show_bug.cgi?id=734837
|
|
|
|
| |
Also updated the unit tests so they don't fail with the new tap system
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| |
| |
| | |
This is quite an API break, but the previous API was confusing and a monster,
so this was really necessary.
The unit tests have been put in place to make sure things work correctly too.
|
| |
| |
| |
| | |
Use $top_srcdir, not relative links
|
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Use CC_CHECK_FLAGS_APPEND m4 macro to make sure GCC supports flags
This is after finding out that some platforms or versions of GCC don't
support flags like -Wmaybe-uninitialized
The attributes.m4 is stolen from systemd who stole it from xine-lib.
|
| |
| |
| |
| | |
get_heuristic()
|
| | |
|
| | |
|