Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upNightly macOS can't initialize GStreamer #27293
Closed
Labels
Comments
Member
jdm
commented
Jul 16, 2020
|
|
I believe the issue here is that the gstreamer shared libraries that are bundled in the nightly build come from the build machines which are still on gstreamer 1.16.2, and my local machine has gstreamer 1.16.3. |
|
We probably need to bundle more shared libraries from the build machines to avoid this situation. |
bors-servo
added a commit
that referenced
this issue
Jul 16, 2020
Make gstreamer packaging explicit This change aligns Windows and macOS in terms of loading an explicit set of included plugins when initializing gstreamer. It also creates a single source of truth - the set of expected plugins is generated in a build script by the same python code that is used for packaging, so it should be impossible for platforms relying on this system to get out of sync. Fixes #27293
bors-servo
added a commit
that referenced
this issue
Jul 16, 2020
Make gstreamer packaging explicit This change aligns Windows and macOS in terms of loading an explicit set of included plugins when initializing gstreamer. It also creates a single source of truth - the set of expected plugins is generated in a build script by the same python code that is used for packaging, so it should be impossible for platforms relying on this system to get out of sync. Fixes #27293
bors-servo
added a commit
that referenced
this issue
Jul 17, 2020
Make gstreamer packaging explicit This change aligns Windows and macOS in terms of loading an explicit set of included plugins when initializing gstreamer. It also creates a single source of truth - the set of expected plugins is generated in a build script by the same python code that is used for packaging, so it should be impossible for platforms relying on this system to get out of sync. Fixes #27293
bors-servo
added a commit
that referenced
this issue
Jul 17, 2020
Make gstreamer packaging explicit This change aligns Windows and macOS in terms of loading an explicit set of included plugins when initializing gstreamer. It also creates a single source of truth - the set of expected plugins is generated in a build script by the same python code that is used for packaging, so it should be impossible for platforms relying on this system to get out of sync. Fixes #27293
bors-servo
added a commit
that referenced
this issue
Jul 17, 2020
Make gstreamer packaging explicit This change aligns Windows and macOS in terms of loading an explicit set of included plugins when initializing gstreamer. It also creates a single source of truth - the set of expected plugins is generated in a build script by the same python code that is used for packaging, so it should be impossible for platforms relying on this system to get out of sync. Fixes #27293
bors-servo
added a commit
that referenced
this issue
Jul 17, 2020
Make gstreamer packaging explicit This change aligns Windows and macOS in terms of loading an explicit set of included plugins when initializing gstreamer. It also creates a single source of truth - the set of expected plugins is generated in a build script by the same python code that is used for packaging, so it should be impossible for platforms relying on this system to get out of sync. Fixes #27293
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment