Windows questions.

[Jeff Shanab]

I always had developer package downloaded.

I was able to get it to work.

The windows installation is missing a lot compared to the linux ones.
Plugins do not need to be built with meson, i was able to create a Visual
Studio dll project, copy in the .h and .c files and build.


I only had to add the Defines that normally come from the build system in
the plugins.c file where it calls the macro GST_PLUGIN_DEFINE

//@JFS normally from meson
#define VERSION "0.0.0"
#define PACKAGE "rtponvif"
#define GST_PACKAGE_NAME "GStreamer rtp onvif filter"
#define GST_PACKAGE_ORIGIN "http://gstreamer.net/"

Copying this to the folder along side the other plugins (in the
gstreamer/lib folder NOT the bin folder pffft) allowed the
example(test-onvif-client) to run.

I am now trying to create a single folder with all the dlls and plugins to
allow it to be used during testing to exercise a server.
It is proving difficult. Even though all the dlls are there and Dependency
walker is happy, it always bails out unable to create rtspsrc element.
probably a hidden dependency that is only at LoadLibrary time.

On Wed, Jan 6, 2021 at 3:18 PM gotsring <gotsring at live.com> wrote:

> I just started using Gstreamer on Windows also. I'm using the 1.18.2 MSVC
> 64-bit binaries from the GStreamer download page. I haven't messed with
> altering GStreamer plugins themselves, so someone else will have to talk on
> ONVIF support.
>
>
> Jeff Shanab wrote
> > 1) Are gst-plugins-bad only available on windows if you build from
> source?
>
> Doing a complete install of the runtime and dev installers, I have plugins
> bad out of the box (I'm using h264parse). However, I don't see anything
> onvif-related either, so may be OS-dependent?
>
>
> Jeff Shanab wrote
> > 2) Is there a separate package, artifactory, etc for plugin binaries and
> > headers?
>
> The runtime installer only really has binary files (there are some other
> misc items). To develop anything using GStreamer, you should also run the
> development installer.  Just double-check your environment variables and
> PATH to make sure everything is being found (easiest to just install to
> C:\gstreamer). FYI, when I did a "Complete" install, the install directory
> was something else; I had to change it to C:\gstreamer
>
>
> Jeff Shanab wrote
> > 3) Are plugins on top of core and can be built in VS, or do we need the
> > entire meson/MSYS2 build
> >    A) I do not know how to build GStreamer on Windows. Last try went
> > horribly wrong with old instructions. :-(
>
> To develop anything WITHIN GStreamer, I believe you have to build with
> Cerbero and target Visual Studio. I used the build instructions in the
> README without issue, it just took a while. Last I heard, Cerbero is how
> the
> binaries are produced for the download page, so I think this is the
> recommended build process. Last I tried meson, it sort of worked, but I
> didn't mess with it that much.
>
>
>
> --
> Sent from: http://gstreamer-devel.966125.n4.nabble.com/
> _______________________________________________
> gstreamer-devel mailing list
> gstreamer-devel at lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/gstreamer-devel/attachments/20210106/5a8c2371/attachment.htm>