Questions about MSVC build

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Questions about MSVC build

David Ing
I have been looking at the msvc build for 1.16.0 and I noticed that a lot of things are missing compared to the mingw build.

My questions are:
  • Is someone keeping a list of things which are not being built with the MSVC build?
    • If so where is it?
  • Is someone actively working on improving the MSVC build (so that it becomes fully featured)?
    • If so, when might we expect a fully featured MSVC build?
  • Has anyone experimented with adding MINGW components as stand-ins for the missing components of the MSVC build?
    • Is that likely to work if I tried it?

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Questions about MSVC build

Nirbheek Chauhan
On Thu, Jun 20, 2019 at 2:55 AM David Ing <[hidden email]> wrote:
>
> I have been looking at the msvc build for 1.16.0 and I noticed that a lot of things are missing compared to the mingw build.
>

What things have you noticed to be missing? The MSVC build is almost
entirely feature-complete. Note that the DLL naming is different in
the MSVC build, as noted on the download page. Instead of libfoo.dll
everything built with MSVC is foo.dll instead.

> My questions are:
>
> Is someone keeping a list of things which are not being built with the MSVC build?
>
> If so where is it?
>

The full list is here:
https://gitlab.freedesktop.org/gstreamer/cerbero/issues/121

> Is someone actively working on improving the MSVC build (so that it becomes fully featured)?
>
> If so, when might we expect a fully featured MSVC build?
>

I am not aware of anyone doing this for the plugins listed in the
issue above. You're welcome to start working on it if you wish to :)

> Has anyone experimented with adding MINGW components as stand-ins for the missing components of the MSVC build?
>
> Is that likely to work if I tried it?
>

This is already the case for the majority of plugins with external
dependencies which are still built with Autotools and MinGW.

Cheers,
Nirbheek
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Questions about MSVC build

David Ing
> What things have you noticed to be missing? The MSVC build is almost
>  entirely feature-complete. Note that the DLL naming is different in
>  the MSVC build, as noted on the download page. Instead of libfoo.dll
>  everything built with MSVC is foo.dll instead. 
 
I stand corrected.  I had an inventory script which apparently chokes because the filenames have changed.

When I inventoried the gstreamer elements using `gst-inspect-1.0` I only noticed a minor difference in the plugin names for two gstreamer elements.
  • filesink <--> fdsink
  • filesrc <--> fdsrc
Followup question:  Why did the name of these two gstreamer elements change?

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Questions about MSVC build

Mathieu Duponchelle
On 6/20/19 12:10 AM, David Ing wrote:
> What things have you noticed to be missing? The MSVC build is almost
>  entirely feature-complete. Note that the DLL naming is different in
>  the MSVC build, as noted on the download page. Instead of libfoo.dll
>  everything built with MSVC is foo.dll instead. 
 
I stand corrected.  I had an inventory script which apparently chokes because the filenames have changed.

When I inventoried the gstreamer elements using `gst-inspect-1.0` I only noticed a minor difference in the plugin names for two gstreamer elements.
  • filesink <--> fdsink
  • filesrc <--> fdsrc
Followup question:  Why did the name of these two gstreamer elements change?

These are not the same elements

_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
Reply | Threaded
Open this post in threaded view
|

Re: Questions about MSVC build

Nirbheek Chauhan
In addition, fdsrc/fdsink are not available with MSVC because they use
APIs that are only available with MinGW. filesrc/filesink are still
available with MSVC.

Cheers,
Nirbheek

On Thu, Jun 20, 2019 at 3:55 AM Mathieu Duponchelle
<[hidden email]> wrote:

>
> On 6/20/19 12:10 AM, David Ing wrote:
>
> > What things have you noticed to be missing? The MSVC build is almost
> >  entirely feature-complete. Note that the DLL naming is different in
> >  the MSVC build, as noted on the download page. Instead of libfoo.dll
> >  everything built with MSVC is foo.dll instead.
>
> I stand corrected.  I had an inventory script which apparently chokes because the filenames have changed.
>
> When I inventoried the gstreamer elements using `gst-inspect-1.0` I only noticed a minor difference in the plugin names for two gstreamer elements.
>
> filesink <--> fdsink
> filesrc <--> fdsrc
>
> Followup question:  Why did the name of these two gstreamer elements change?
>
>
> These are not the same elements
> _______________________________________________
> gstreamer-devel mailing list
> [hidden email]
> https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel
_______________________________________________
gstreamer-devel mailing list
[hidden email]
https://lists.freedesktop.org/mailman/listinfo/gstreamer-devel