gst recipes: Disable plugins when building with MSVC
Some libraries have issues that cause us to be unable to include their headers or link to their libraries when building with MSVC. Disable them when we're building with MSVC on Windows.
With this, you can produce a mostly-complete gstreamer-1.0 package that is built with MSVC on Windows.
Merge request reports
Activity
- Resolved by Nirbheek Chauhan
- Resolved by Nirbheek Chauhan
I didn't intend this PR to fix issues with plugins that don't build with MSVC, but to make the
visualstudio
variant usable by disabling the things that don't build when that variant is enabled.There may be low-hanging fruit to fix in here, but having it upstream is a good way to get people to try things out and fix them rather than have it all in a private branch and telling people to use that. The default configuration doesn't change.
I think the comments are self-explanatory and the problems easily reproducible, but I can file issues. Is there anything other than
srt
andwebrtcdsp
that stands out to you?Strange, we do include Winsock2.h (even though lower case in the code) as per https://docs.microsoft.com/en-us/windows/desktop/api/winsock/ns-winsock-timeval
gstdtlsconnection.c(375): error C2079: 'timeout' uses undefined struct 'timeval'
That build failure has been fixed in gst-plugins-bad@b1509b10. I can reproduce it with code prior that change.
Thanks Jakub, that explain all the questions. @nirbheek time to rebase ?
That build failure has been fixed in gst-plugins-bad@b1509b10. I can reproduce it with code prior that change.
Thanks for the heads-up, I've rebased the branch. I've also added two new commits that fix GIO module loading.
added 1 commit
- 4a182a39 - gstreamer.recipe: Explicitly enable dbghlp on MSVC
@nirbheek just a note that my review was only requesting that each disabled element have an associated issue reported (in the respective upstream project if it's not GST fault). I'm happy you are fixing some of it, but I'm fine if some of it does not work for a first this release. Well document this in the release notes as know issues.
@ndufresne Ah, that wasn't clear to me. I will use my judgement on which libraries to open upstream bugs about, and will add the rest to a single tracker Cerbero issue.
mentioned in issue #121 (closed)