- Apr 27, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Apr 24, 2017
-
-
Tim-Philipp Müller authored
From 60aeef6 to 48a5d85
-
- Apr 21, 2017
-
-
-
-
Thibault Saunier authored
-
- Apr 20, 2017
-
-
Thibault Saunier authored
-
- Apr 19, 2017
-
-
Sebastian Dröge authored
It's otherwise appearing many, many times in logs and usually is nothing you're interested in.
-
-
Yasushi SHOJI authored
This unbalanced closing parenthesis is leftover from the commit 8b739d91. It used to wrap the caps but we don't seem to do that in the current code. So, just remove it. No functionality has been changed. https://bugzilla.gnome.org/show_bug.cgi?id=781484
-
- Apr 13, 2017
-
-
Rico Tzschichholz authored
-
- Apr 12, 2017
-
-
Thibault Saunier authored
Avoiding build failure like https://ci.appveyor.com/project/thiblahute/gst-build-ge9m5/build/1.0.2857
-
- Apr 11, 2017
-
-
Tim-Philipp Müller authored
-
Tim-Philipp Müller authored
And fix includes in docs to just include the main header (the include for the proxycontrolbinding was wrong in the docs).
-
Tim-Philipp Müller authored
-
-
-
- Apr 10, 2017
-
-
Tim-Philipp Müller authored
From 39ac2f5 to 60aeef6
-
Olivier Crête authored
Some GstStructure properties default to NULL, so it should be a supported value. With unit test.
-
Sebastian Dröge authored
-
Rico Tzschichholz authored
-
- Apr 09, 2017
-
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Apr 08, 2017
-
-
Tim-Philipp Müller authored
Use g_object_new() instead which nowadays has a shortcut for the no-properties check. It still does an extra GType check in the function guard, but there's a pending patch to remove that and it's hardly going to be a performance issue in practice, even less so on a system that's compiled without run-time checks. Alternative would be to move to the new g_object_new_properties() with a fallback define for older glib versions, but it makes the code look more unwieldy and doesn't seem worth it. Fixes deprecation warnings when building against newer GLib versions. https://bugzilla.gnome.org/show_bug.cgi?id=780903
-
- Apr 07, 2017
-
-
Olivier Crête authored
-
Sebastian Dröge authored
-
Sebastian Dröge authored
-
- Apr 06, 2017
-
-
Olivier Crête authored
Putting NULL for those is a valid serialization for the NULL value.
-
- Apr 05, 2017
-
-
Sebastian Dröge authored
They were (signed!) gint64 before because of G_GINT64_CONSTANT() already and they are actually used in signed calculations. With this change we at least ensure that an integer type of the correct size is used for GI (it was using gint before).
-
Sebastian Dröge authored
-
Sebastian Dröge authored
This makes C++ compilers a bit more happy without having the user of the constants cast. It also provides the correct type information to GI. https://bugzilla.gnome.org/show_bug.cgi?id=780923
-
Sebastian Dröge authored
-
Sebastian Dröge authored
Storing a -1 inside an unsigned integer confuses GIR based bindings generators.
-
- Apr 04, 2017
-
-
Nicolas Dufresne authored
In GES, the summary refers to options that are only available when built against gst-valdiate. Those where picked by our regex. This patch add a initial grep to try and filter-out as best as possible the content to which we will extract the command list.
-
Nicolas Dufresne authored
-
Nicolas Dufresne authored
This patch reorganize the bash completion scripts in order to install the binary helper (gst-completion-helper) in libexec path rather then share folder. Most Linux hierarchy compliance requires that no binary executable are placed in share. We also cleanup the unused .pc entries and remove copy pasted parts of the script. Note that other project including the common helper, should now use $_GST_HELPER to read the binary executable gst-completion-helper. This helper is not longer version, as it is placed in a versionned subfolder (libexec/gstreamer.10) just like the other helpers (scanner and ptp).
-
- Mar 31, 2017
-
-
-
Vincent Penquerc'h authored
The issue happens when the structure is printed by the logging subsystem: the object is included in the log, and this will cause the full object printout to be done there. However, after dispose, the queue was already cleared, so the access to it (to print the object) would assert, as the queue was already freed. The patch changes it so that the queue is merely empty, and only freed in _finalize. https://bugzilla.gnome.org/show_bug.cgi?id=776293
-