This reverts commit c0a6825f.

Openh264 makefiles install to $(DESTDIR)/$(PREFIX) so they
already prepend a /

Andy Devar authored 8 years ago and Sebastian Dröge committed 8 years ago

Windows a) requires quotes around commands if you | them and b) remembers
empty quotes in Makefiles and confuses the shell with them.

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

Need to prepend a / when converting from a Windows-style path to a UNIX-style one

On OSX they apparently end up as literal '\n' in the code instead of newlines.

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

Windows has no cat so it doesn't work. We lose some symmetry in the code in
exchange for Windows portability.

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

Sebastian Dröge authored 8 years ago and Olivier Crête committed 8 years ago

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

Based on a patch by Milos Pesic <msg4misa@gmail.com>

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

Get the correct symbol via dlsym() instead of letting the linker figure it
out. Letting the linker do it can bring us into infinite recursion calling
into our very own weak symbol.

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

Nirbheek Chauhan authored 8 years ago and Sebastian Dröge committed 8 years ago

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

Nirbheek Chauhan authored 8 years ago and Sebastian Dröge committed 8 years ago

Patches are taken from upstream. Found by inspecting upstream commit logs.

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

Workaround for Android <21 making signal() an inline function
around bsd_signal(), and Android >= 21 not having any bsd_signal()
symbol but only signal()

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

I'm sure I saw that reported in Bugzilla today or yesterday, or on the mailing
list. But can't find it now :)

Ursula Maplehurst authored 8 years ago and Tim-Philipp Müller committed 8 years ago

libgstvideo4linux2.a wasn't being included as a result

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

Xavier Claessens authored 8 years ago and Tim-Philipp Müller committed 8 years ago

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

Xavier Claessens authored 8 years ago and Tim-Philipp Müller committed 8 years ago

This avoids having user settings messing up our build.

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

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

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

This tinyalsa repo doesn't seem to do tags or releases.

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

Not that anything changed in the last 9 years.

Same as main orc recipe.

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

Spotted by Xavier Claessens

long is 32 bits on Win64, GType 64 bits.

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

Xavier Claessens authored 8 years ago and Tim-Philipp Müller committed 8 years ago

They fail to build with newer livetex.

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

Xavier Claessens authored 8 years ago and Tim-Philipp Müller committed 8 years ago

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

git-for-windows will error out with 'Tell me who you are'
otherwise, if no global user config exists.

Nirbheek Chauhan authored 8 years ago and Tim-Philipp Müller committed 8 years ago

Otherwise git may fail to apply patches to our unpacked
source trees if there's no valid global git user config
yet, with "fatal: empty ident name (for ...) not allowed".