GitLab

And add getpluginsdir here as it is shared by many modules

This reverts commit b18d8206.

Causes problems for distros with /bin/sh = dash

Preserve multiword arguments that are to be passed
to configure, and quote them in the generated
autoregen.sh

That wasn't meant to go in, it's for all modules after all.

These are system and configuration dependent.

Recently noticed that gtk-doc stopped to extract the internal
documentation (appeared just API, but no description).

The problem seems to be a regression from commit f363b320, where the
expasion of the variable _source_dir is expanded using parentheses,
which are used for command substitution, when the variable need to
be a string expansion, and for that brace are needed by the shell.

https://bugzilla.gnome.org/show_bug.cgi?id=768571

As some places we where assuming a single directory. This caused some
plugins documentation to be ignored.

On osx, make check in gstreamer directory currently outputs:
"error: argument unused during compilation: '-pthread'".

This new ax_pthread.m4 adds -Qunused-arguments when needed.

Source:
http://www.gnu.org/software/autoconf-archive/ax_pthread.html

History:
http://git.savannah.gnu.org/gitweb/?p=autoconf-archive.git;a=history;f=m4/ax_pthread.m4

https://bugzilla.gnome.org/show_bug.cgi?id=747954

https://bugzilla.gnome.org/show_bug.cgi?id=763764

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=761718

Fixes https://bugzilla.gnome.org/show_bug.cgi?id=762707

The exported symbols will depend on the backends built
and be different from platform to platform. Should probably
be the win32 symbols anyway, which is not the case at the
moment. So for now just show any diff but not fail.

Set it as part of the AM_TESTS_ENVIRONMENT variable so that it
is the same when running make-check from the top-level dir or
when running the element.check variations

https://bugzilla.gnome.org/show_bug.cgi?id=761472

On certain filesystems like FAT, NTFS and some network file systems,
symlinks are not supported. In those case, installing the pre-commit
hook fails and leaves the developers with having to run the style
checker manually.

Instead, fallback to copy. This should enable the commit hook for
users of filesystems and certain OSs where symlinks are not supported.

https://bugzilla.gnome.org/show_bug.cgi?id=759089

the 2-parameter invocation:
AG_GST_SET_PACKAGE_RELEASE_DATETIME([yes], [YYYY-MM-DD])
is greping the first parameter instead of the second.

https://bugzilla.gnome.org/show_bug.cgi?id=739079

https://bugzilla.gnome.org/show_bug.cgi?id=739079

https://bugzilla.gnome.org/show_bug.cgi?id=739079

Something is not right with these checks, they sometimes lead
to build failures on OSX/iOS like e.g.
Undefined symbols for architecture i386:
"rrwarn=%all,no%E_EMPTY_DECLARATION,no%E_STATEMENT_NOT_REACHED,no%E_ARGUEMENT_MISMATCH,no%E_MACRO_REDEFINED,no%E_LOOP_NOT_ENTERED_AT_TOP", referenced from:
implicit entry/start for main executable
ld: symbol(s) not found for architecture i386

Let's just remove the -Wall/-Werror support in case
of this compiler which is most likely completely unused
anyway these days. Code will still compile just fine as
before (hopefully), it's just that we don't get extra
warnings.

Assertions are useful to have in any case, and we were abusing the #define for
adding extra checks to our code. Let's do it properly!

https://bugzilla.gnome.org/show_bug.cgi?id=756870

Turns out the original upstream 2.4.2 does work, it's the 2.4.2
shipping with Ubuntu that breaks.

This reverts commit d689b7e7.

Earlier versions now fail with the switch to autoreconf.

https://bugzilla.gnome.org/show_bug.cgi?id=754690

"match-leak-kinds: possible" is a recent valgrind addition,
and valgrind 3.7.0 errors out on it.

https://bugzilla.gnome.org/show_bug.cgi?id=747612

This is leaked intentionally in glib.

Otherwise valgrind checks will fail if there's a "==" anywhere in the
output, which can easily happen when running with debug logging
enabled, for example.

Generate a sections file. We don't merge it yet until we cleaned all the modules.

This is the appropriate value to use for g-ir-scanner option
--add-init-section. This is also a single location in case we
get it wrong again.

Since all we want is to get the include into the docbook files, run an extra
step to patch the generated docbook files.

We don't have any hand-written docs in tmpl files. Stop generating them with
gtkdoc and just write the minimal files ourself.

Add GTKDOC_RUN envar that can be used to run the introspection via libtool.
Define GTKDOC_{CC,LD,RUN} here to avoid repetition in each docs/Makefile.am.

We already have plenty of suppressions related to do_lookup_x but this one
seems to be needed on my system as well.

https://bugzilla.gnome.org/show_bug.cgi?id=749831

We just want to know if we have a match or not.

Don't run autopoint just because a po directory exist, also
check for AM_GNU_GETTEXT_VERSION in configure.ac.

https://bugzilla.gnome.org/show_bug.cgi?id=748058

No need to check the versions there. pkg-config 0.8 was
released in 2003. autoconf version checks will be made
by autoreconf based on our requirement in configure.ac,
and it will error out for us in that case.

So just check for presence of these tools and get rid
of a whole lot of code.