Include vcpkg libs in Windows build

[Nirbheek Chauhan]

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 <gotsring at live.com> 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?
>