GitLab

Don't suggest deprecated method in the desction docs and try to be more helpful
in other places by suggesting related functions.

Make it more obvious that one should pass the template name.

The MAX macro expands to code that checks if an unsigned integer is < 0.

Fixes warning #186: pointless comparison of unsigned integer reported by ICC.

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

Fixes warning #188: enumerated type mixed with another type reported by ICC.

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

Fixes warning #188: enumerated type mixed with another type reported by ICC.

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

Fixes warning #188: enumerated type mixed with another type reported by ICC.

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

Fixes warning #188: enumerated type mixed with another type reported by ICC.

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

Fixes a warning reported by ICC.

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

Use them to fix warnings when building with ICC.

API: GST_CAPS_FLAGS_NONE

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

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

Instead of checking for valid utf-8 element-details every time we create
elements (from plugin-init or registry), do it before we save the registry.
Fixes #656193.

Iterate source- and sink-pads separately to ensure that the graph reflects the
upstream/downstream order. Fixes #643269

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

Fixes: #653172.
Signed-off-by: David Schleef <ds@schleef.org>

G_CONST_RETURN will be deprecated soon.

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

See #651514 for details.  It's apparently impossible to write code
that avoids both type punning warnings with old g_atomic headers and
assertions in the new.  Thus, macros and a version check.

G_CONST_RETURN will be deprecated soon.

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

The warning is never fatal, because we don't use -Werror for the
parser helper library build, but the warnings are annoying anyway.

See #651514 for details.  It's apparently impossible to write code
that avoids both type punning warnings with old g_atomic headers and
assertions in the new.  Thus, macros and a version check.

Previously this was only done in the is_subset() check but
having it only there brings us into definition-hell where
"1" and "{1}" are subset of each other but not equal.

For example "{ 1 }" and "1" are not strictly equal but
both are a subset of each other. Also add a unit test
for this.

API: gst_caps_is_subset_structure()

This allows to check if a structure is a subset of given
caps without allocating a new caps instance for it.

API: gst_structure_is_subset()

..and as a result gst_caps_is_equal() and others.

This now only checks if for every subset structure there is
a superset structure in the superset caps. Previously we were
subtracting one from another, creating completely new caps
and then even simplified them.

The new implemention now is about 1.27 times faster and doesn't
break the -base unit tests are anything anymore.

Caps A are a subset of caps B even if caps B doesn't
have all fields of caps A.

Also add a unit test for this.

This reverts commit 32248a9b.

This breaks some tests in -base and the failures should
be fixed first.

..and as a result gst_caps_is_equal() and others.

This now only checks if for every subset structure there is
a superset structure in the superset caps. Previously we were
subtracting one from another, creating completely new caps
and then even simplified them.

The new implemention now is about 1.27 times faster.