[vlc-devel] uncertain: whether to develop plugin for a custom codec.

Rafaël Carré funman at videolan.org
Sat Oct 19 11:49:51 CEST 2013


Le 19/10/2013 11:31, Jean-Baptiste Kempf a écrit :
> On 19 Oct, BGB wrote :
>> minor comments:
>> some of the headers contain things which are not particularly friendly to
>> Visual Studio / MSVC (*1), in particular things like some of the static
>> functions within headers declaring variables within the executable part of
>> the function body (as opposed to declaring all variables at the top, prior
>> to any executable statements), as well as the use of the 'inline' keyword.
> 
> Not our problem.
> Use a better compiler.

That's true, you should use gcc, make sure you have read
https://wiki.videolan.org/Win32Compile

For rebuilding one module the process goes like this:

cd vlc/contrib/win32/ffmpeg
### patch
make install
# now your new static libavcodec.a is installed in
vlc/contrib/i686-w64-mingw32
cd vlc/build/modules
make libavcodec_plugin.la
# now your new vlc avcodec plugin dll is in .libs/libavcodec_plugin.dll
# copy that dll in your install folder inside plugins/codec and you're
good to go

> And you know, VS2013 is out with C99 support.

yeah, "support" :)

> Best regards,
> 




More information about the vlc-devel mailing list