So that the -base libs can figure out the right include paths for the
gobject-introspection tools even if core got installed into a prefix
that's not the same prefix as gobject-introspection is installed in
or it's being build in an uninstalled gstreamer setup.
Attempt to add back support for builddir != srcdir. Use absolute paths
instead of relative paths based on pcfiledir this time to make things
clearer - there's not really any need for uninstalled trees to be
relocatable without re-running configure.
I don't know how this ever worked, as it seems to put -I./..
and -I./../libs verbatim into the includes, at least with
current autotools versions.
This reverts commit 279a80ff27.
If we force -DG_THREADS_MANDATORY onto apps, then g_thread_supported()
will always evaluate to TRUE, so the typical thread initialisation
boilerplate code if (!g_thread_supported()) g_thread_init(NULL); will
no longer work, and the threading system not be initialised and us
printing a warning in gst_init. This may be fine in most cases, since
late initialisation is allowed and automatically done in g_type_init()
since GLib 2.23.2, but let's be cautious and only use this define when
compiling GStreamer itself.
See #608398.
We require threads to be supported in any case and defining this
will simplify the mutex, condition variable, etc. macros from gthread
to not always check if threads are really supported.
Fixes bug #607481.
When you use gstreamer uninstalled and build outside
the source tree, the includes need to be specified for
both the source tree and the build tree.
Signed-off-by: David Schleef <ds@schleef.org>
Original commit message from CVS:
* pkgconfig/gstreamer-uninstalled.pc.in:
* pkgconfig/gstreamer.pc.in:
Remove -lgstcontrol-0.10 which never worked anyway as the lib is
called gstcontroller-0.10.
Original commit message from CVS:
Port some changes from 0.6.0/0.6.1 back to HEAD (.pc files moved to pkg-config/, .m4 file moved from plugins to core)
