I was able to successfully build and use GStreamer 1.18 on Windows 10 using
the process listed here: https://www.collabora.com/news-and-blog/blog/2019/11/26/gstreamer-windows/ However, some gstreamer deps are not found, such as openssl and gtk3. I already have these installed and available to Visual Studio 2019 using vcpkg (tested install with other projects), and because I am building GStreamer with the x64 Native Tools for Command Prompt for Visual Studio, would they not be available while building? I tried adding the vcpkg bin dir to PATH, but that did nothing. There doesn't appear to be a relevant pkg-config file that I can add. Is there a way to use packages from vcpkg? Previous questions here indicate that duplicate glib instances can cause issues, so is this even recommended? -- Sent from: http://gstreamer-devel.966125.n4.nabble.com/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Hi,
Please don't follow the instructions on that blog post. That is not the official way to build gstreamer on Windows, and the strange hybrid setup in that post should only be attempted by advanced users. I'm actually really annoyed that it has such a generic title implying that it should be used by everyone. The recommended way to build GStreamer is with: https://gitlab.freedesktop.org/gstreamer/cerbero/#description The built output from Cerbero is also provided as release binaries: https://gstreamer.freedesktop.org/download/#windows However, none of this provides gtk on Windows. That's being worked on here: https://gitlab.freedesktop.org/gstreamer/cerbero/-/merge_requests/585 We do not recommend vcpkg for many reasons, some of which are: 1. vcpkg builds are unsupported, they do not work with upstream projects and have written their own build files for everything, which are badly broken in many cases 2. GStreamer built with Cerbero yields the best experience with the most number of plugins and all toolchain issues handled 3. You can only safely load one instance of glib in a process, so you cannot mix and match GStreamer built with Cerbero with GObject libraries (such as GTK) from other sources Cheers, Nirbheek On Wed, Sep 23, 2020 at 11:17 PM gotsring <[hidden email]> wrote: > > I was able to successfully build and use GStreamer 1.18 on Windows 10 using > the process listed here: > https://www.collabora.com/news-and-blog/blog/2019/11/26/gstreamer-windows/ > > However, some gstreamer deps are not found, such as openssl and gtk3. I > already have these installed and available to Visual Studio 2019 using vcpkg > (tested install with other projects), and because I am building GStreamer > with the x64 Native Tools for Command Prompt for Visual Studio, would they > not be available while building? > > I tried adding the vcpkg bin dir to PATH, but that did nothing. There > doesn't appear to be a relevant pkg-config file that I can add. Is there a > way to use packages from vcpkg? Previous questions here indicate that > duplicate glib instances can cause issues, so is this even recommended? > gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Thanks for the info, I'll switch to Cerbero. I saw this a bit late, but in
the interim, I had abandoned VCPKG and tried building Gtk and deps from source, most of which also use meson, but there always seems to be some little thing wrong. Quick question: The basic process of that blog post seems to echo the README of the gst-build project: get meson and ninja, then run the build. Is Cerbero still preferred over meson on Window? -- Sent from: http://gstreamer-devel.966125.n4.nabble.com/ _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
On Wed, Sep 30, 2020 at 4:00 AM gotsring <[hidden email]> wrote:
> > Thanks for the info, I'll switch to Cerbero. I saw this a bit late, but in > the interim, I had abandoned VCPKG and tried building Gtk and deps from > source, most of which also use meson, but there always seems to be some > little thing wrong. > > Quick question: The basic process of that blog post seems to echo the README > of the gst-build project: get meson and ninja, then run the build. Is > Cerbero still preferred over meson on Window? > If you need to build GStreamer with a custom configuration, the easiest option is to use Cerbero, which is a meta-build system. It will download all the dependencies for you (including most of the build-tools), build them with Autotools, CMake, or Meson (as appropriate), and output an MSI installer. gst-build is more useful when you want to hack on gstreamer since it allows you to quickly edit files in-place and build / test your changes with a single command. _______________________________________________ gstreamer-devel mailing list [hidden email] https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel |
Free forum by Nabble | Edit this page |