[gst-devel] New GStreamer binaries for Windows based on OAbuild.

Andoni Morales ylatuya at gmail.com
Thu Jan 8 16:15:33 CET 2009


>
>
> For ffmpeg for example, no. They are syntax changes needed to make
> msvc happy but that compile just fine with gcc. And they are A LOT
> (thousands of lines).
>

I don't use MSVC to build ffmpeg. All the external libraries are built using
mingw/msys and then I add to the OAbuild "builddeps" dir the includes, dll's
and impot libraries used by OABuild.
The problem with the original OABuild method is that all the external
libraries are built using MSVC, and that's why it doesn't provide support
for many external plugins, because not all the external dependencies can be
compiled using MSVC.

The changes in the GStreamer code are just a few lines. Take a look at
http://codeanticode.wordpress.com/2008/09/12/the-gstreamer-adventure-part-i-creating-a-windows-installer/.
For the ffmpeg plugin the lines to changes are 4:


   - In gstffmpegenc.c do: replace in_plugin = first_avcodec; by in_plugin =
   av_codec_next(NULL); and in_plugin = in_plugin->next; by in_plugin =
   av_codec_next(in_plugin);
   - In gstffmpegdec.c, do: replace in_plugin = first_avcodec; by in_plugin
   = av_codec_next(NULL); and in_plugin = in_plugin->next; by in_plugin =
   av_codec_next(in_plugin);

So these changes can be pusshed upstream
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/gstreamer-devel/attachments/20090108/8e874fa8/attachment.htm>


More information about the gstreamer-devel mailing list