Build FFmpeg libraries in Windows

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Build FFmpeg libraries in Windows

m.kamalasubha m.kamalasubha
Hello,
  I am trying to build static libraries (.lib) for FFmpeg 3.3 version in
Windows 10.
I followed the steps outlined in the link given below,
https://trac.ffmpeg.org/wiki/CompilationGuide/MSVC
and used Visual Studio 2015 version.
In order to generate static libs, I changed the configure options from
"--enable-shared --disable-static" to "--enable-static --disable-shared".
But, it always generates libraries in ".a" format.
How to generate static libraries in ".lib" format?

Thanks in advance ...
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Build FFmpeg libraries in Windows

Moritz Barsnick
On Thu, Nov 30, 2017 at 18:46:51 +0530, m.kamalasubha m.kamalasubha wrote:
> for FFmpeg 3.3 version

An particular reason for not choosing something newer?

> In order to generate static libs, I changed the configure options from
> "--enable-shared --disable-static" to "--enable-static --disable-shared".
> But, it always generates libraries in ".a" format.

A patch to change this was posted to the ffmpeg-devel mailing list
recently:
http://ffmpeg.org/pipermail/ffmpeg-devel/2017-September/216916.html

but it was not accepted, because it may break existing workflows.

> How to generate static libraries in ".lib" format?

I guess what you can do is to apply the patch provided in the quoted
e-mail, or just rename those files to *.lib yourself after compilation.

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Build FFmpeg libraries in Windows

m.kamalasubha m.kamalasubha
Thanks Moritz..

>An particular reason for not choosing something newer?
 FFmpeg 3.3 version is required for my work.

>A patch to change this was posted to the ffmpeg-devel mailing list
>recently:
>http://ffmpeg.org/pipermail/ffmpeg-devel/2017-September/216916.html
>
>but it was not accepted, because it may break existing workflows.

How to use the patch ? Is there any steps available ?
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Build FFmpeg libraries in Windows

Moritz Barsnick
On Fri, Dec 01, 2017 at 13:33:43 +0530, m.kamalasubha m.kamalasubha wrote:
> How to use the patch ? Is there any steps available ?

To apply the patch, you need a tool named "patch".

Unpack the sources, change into the source directory, and issue
$ patch -p1 -i /path/to/patchfile.txt

Then do the regular ./configure, make.

Moritz
_______________________________________________
ffmpeg-user mailing list
[hidden email]
http://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".