Re: [FFmpeg-user] How to build for static ffmpeg executable
On Thu, Jan 21, 2016 at 15:54:08 +, John Pompeii wrote: > Maybe another way to ask this question is: How do I replicate the > static ffmpeg build for windows? http://ffmpeg.zeranoe.com/faq/ https://ffmpeg.zeranoe.com/blog/?p=414#more-414 "Some key features of this script are: [...] * Allow for a fully static build. [...] Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Thanks for the reply James, 1) I have static libs for all of the media libraries, however the build is not using them. If I simply remove the *.dll.a libs from the /lib directory as suggested in the reply you are referring to (so that only the static libs are available), I get about 10K unresolved symbol errors from the linker2) libgcc_s_seh, libglib, libstd++, libharfbuzz, etc are not external libraries that I can build, they are part of the environment. From what I can tell, the linker is instructed to link to shared libraries, and I cant see anything in the configure script that modifies those options. As I pointed out, the windows binaries that are provided on the ffmpeg site don't contain gcc/gnu dlls and I would assume there is a build configuration that enables that. Or not? Maybe another way to ask this question is: How do I replicate the static ffmpeg build for windows? --john From: James Darnley <james.darn...@gmail.com> To: FFmpeg user questions <ffmpeg-user@ffmpeg.org> Sent: Thursday, January 21, 2016 10:13 AM Subject: Re: [FFmpeg-user] How to build for static ffmpeg executable On 2016-01-21 15:52, John Pompeii wrote: > libbz2-1.dll > libfontconfig-1.dll > libfreetype-6.dll > libgcc_s_seh-1.dll > libglib-2.0-0.dll > libharfbuzz-0.dll > libiconv-2.dll > libintl-8.dll > liblzma-5.dll > libopenjpeg-5.dll > libstdc++-6.dll > libtheoradec-1.dll > libtheoraenc-1.dll > libwavpack-1.dll > libwinpthread-1.dll > libx265.dll > libzimg-2.dll > SDL.dll As you were told on ffmpeg-devel: build these *external* libraries as static libraries. ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
On 2016-01-21 15:52, John Pompeii wrote: > libbz2-1.dll > libfontconfig-1.dll > libfreetype-6.dll > libgcc_s_seh-1.dll > libglib-2.0-0.dll > libharfbuzz-0.dll > libiconv-2.dll > libintl-8.dll > liblzma-5.dll > libopenjpeg-5.dll > libstdc++-6.dll > libtheoradec-1.dll > libtheoraenc-1.dll > libwavpack-1.dll > libwinpthread-1.dll > libx265.dll > libzimg-2.dll > SDL.dll As you were told on ffmpeg-devel: build these *external* libraries as static libraries. signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Am 21.01.2016 um 20:12 schrieb G A: specify -—disable-shared —enable-static that's not enough if your shared libraries are just dll/so files they *all* need to be built static signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Am 21.01.2016 um 20:27 schrieb G A: of course it is enough. it works on unix/osx, i build ffmpeg with 40 plugins from the repo every few days and these flags work. pure nonsense, you need .a files and not .so for static linking [root@buildserver:~]$ rpm -q --filesbypkg x264-latest x264-latest /usr/local/x264/libx264.a x264-latest /usr/local/x264/x264.h x264-latest /usr/local/x264/x264_config.h guess what - libx264 is static linked --extra-ldflags="-I%{_prefix}/local/x264 -L%{_prefix}/local/x264 -ldl' --enable-static --disable-shared the others are *not* - ask "ldd" if you don't believe it [root@buildserver:~]$ ldd /usr/local/bin/ffmpeg linux-vdso.so.1 (0x7ffd5c4f9000) libdl.so.2 => /lib64/libdl.so.2 (0x7f2b15dee000) libpthread.so.0 => /lib64/libpthread.so.0 (0x7f2b15bd2000) libssl.so.10 => /lib64/libssl.so.10 (0x7f2b1596) libcrypto.so.10 => /lib64/libcrypto.so.10 (0x7f2b15568000) libvpx.so.1 => /lib64/libvpx.so.1 (0x7f2b151e1000) libm.so.6 => /lib64/libm.so.6 (0x7f2b14ed8000) libtheoraenc.so.1 => /lib64/libtheoraenc.so.1 (0x7f2b14c98000) libtheoradec.so.1 => /lib64/libtheoradec.so.1 (0x7f2b14a7f000) libmp3lame.so.0 => /lib64/libmp3lame.so.0 (0x7f2b147c6000) liblzma.so.5 => /lib64/liblzma.so.5 (0x7f2b1459d000) libbz2.so.1 => /lib64/libbz2.so.1 (0x7f2b1438d000) libz.so.1 => /lib64/libz.so.1 (0x7f2b14175000) libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x7f2b13f5e000) libc.so.6 => /lib64/libc.so.6 (0x7f2b13b9e000) /lib64/ld-linux-x86-64.so.2 (0x55f75aec) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x7f2b1394f000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x7f2b1366a000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x7f2b13466000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x7f2b13232000) libgomp.so.1 => /lib64/libgomp.so.1 (0x7f2b1301) libogg.so.0 => /lib64/libogg.so.0 (0x7f2b12e09000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x7f2b12bf9000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x7f2b129f5000) libresolv.so.2 => /lib64/libresolv.so.2 (0x7f2b127d9000) libselinux.so.1 => /lib64/libselinux.so.1 (0x7f2b125b5000) libpcre.so.1 => /lib64/libpcre.so.1 (0x7f2b12344000) On Jan 21, 2016, at 11:22, Reindl Haraldwrote: Am 21.01.2016 um 20:12 schrieb G A: specify -—disable-shared —enable-static that's not enough if your shared libraries are just dll/so files they *all* need to be built static signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos: John Pompeii ffmpeg.org> writes: --enable-bzlib --enable-iconv --enable-lzma --enable-zlib These options have no effect, they do not do what you seem to believe they do. I suggest you remove them since you always suggest to remove them *why* do the exist at all in ./configure --help and not only their counterpart --disable-xx? i suggest *you* remove them or stop tell users remove them when there is no harm signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Reindl Harald thelounge.net> writes: > Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos: > > John Pompeii ffmpeg.org> writes: > > > >> --enable-bzlib > >> --enable-iconv > >> --enable-lzma > >> --enable-zlib > > > > These options have no effect, they do not do > > what you seem to believe they do. I suggest > > you remove them > > since you always suggest to remove them *why* do > the exist at all in ./configure --help and not > only their counterpart --disable-xx? [quote] --disable-bzlib disable bzlib [autodetect] --disable-zlib disable zlib [autodetect] --disable-iconv disable iconv [autodetect] --disable-lzma disable lzma [autodetect] [/quote] ??? Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Am 22.01.2016 um 01:07 schrieb Carl Eugen Hoyos: Reindl Harald thelounge.net> writes: i suggest *you* remove them See http://git.videolan.org/?p=ffmpeg.git;a=commitdiff;h=0f05b72f =-) * removed 2013 * most configure scripts are way older * no warnings * just mailing-list complaints signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Am 22.01.2016 um 00:59 schrieb Carl Eugen Hoyos: Reindl Harald thelounge.net> writes: Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos: John Pompeii ffmpeg.org> writes: --enable-bzlib --enable-iconv --enable-lzma --enable-zlib These options have no effect, they do not do what you seem to believe they do. I suggest you remove them since you always suggest to remove them *why* do the exist at all in ./configure --help and not only their counterpart --disable-xx? [quote] --disable-bzlib disable bzlib [autodetect] --disable-zlib disable zlib [autodetect] --disable-iconv disable iconv [autodetect] --disable-lzma disable lzma [autodetect] [/quote] ??? typically configure scripts warn about unkonwn params ffmpeg don't ~/rpmbuild/BUILD/ffmpeg-20160117/generic ~/rpmbuild/BUILD/ffmpeg-20160117 + ../configure --prefix=/usr/local --bindir=/usr/local/bin --mandir=/usr/local/man '--extra-cflags=-I/usr/local/x264 -m64 -O2 -g0 -march=sandybridge -mtune=sandybridge -fopenmp -mfpmath=sse -pipe -fno-strict-aliasing -fomit-frame-pointer -finline-functions -fexceptions -fstack-protector-strong --param=ssp-buffer-size=6 -D_FORTIFY_SOURCE=2 -Wstack-protector -Wformat -Werror=format-security -Ofast -ffast-math -funsafe-math-optimizations -funroll-loops -funswitch-loops -Wno-pointer-sign -minline-all-stringops -flto -fuse-ld=gold -fuse-linker-plugin' '--extra-ldflags=-I/usr/local/x264 -L/usr/local/x264 -ldl -Wl,-z,now -Wl,-z,relro,-z,noexecstack,-fuse-ld=gold -m64 -O2 -g0 -march=sandybridge -mtune=sandybridge -fopenmp -mfpmath=sse -pipe -fno-strict-aliasing -fomit-frame-pointer -finline-functions -fexceptions -fstack-protector-strong --param=ssp-buffer-size=6 -D_FORTIFY_SOURCE=2 -Wstack-protector -Wformat -Werror=format-security -Ofast -ffast-math -funsafe-math-optimizations -funroll-loops -funswitch-loops -Wno-pointer-sign -minline-all-stringops -flto -fuse-ld=gold -fuse-linker-plugin' --enable-pic --enable-lto --ar=gcc-ar --ranlib=true --enable-nonfree --enable-gpl --enable-version3 --enable-libmp3lame --enable-libtheora --enable-libx264 --enable-libvpx --enable-openssl --enable-static --enable-runtime-cpudetect --enable-bzlib --enable-zlib --disable-amd3dnow --disable-amd3dnowext --disable-avdevice --disable-debug --disable-devices --disable-ffplay --disable-ffprobe --disable-ffserver --disable-htmlpages --disable-hwaccels --disable-iconv --disable-libdc1394 --disable-libfaac --disable-libfreetype --disable-libgsm --disable-libopencore-amrnb --disable-libopencore-amrwb --disable-libopencv --disable-libopenjpeg --disable-libopus --disable-librtmp --disable-libschroedinger --disable-libspeex --disable-libvorbis --disable-libxvid --disable-podpages --disable-postproc --disable-protocol=gopher --disable-shared --disable-txtpages nm: /tmp/ffconf.WVafcwrW.o: plugin needed to handle lto object install prefix/usr/local source path /home/builduser/rpmbuild/BUILD/ffmpeg-20160117 signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
John Pompeii ffmpeg.org> writes: > --enable-bzlib > --enable-iconv > --enable-lzma > --enable-zlib These options have no effect, they do not do what you seem to believe they do. I suggest you remove them. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Reindl Harald thelounge.net> writes: > Am 22.01.2016 um 00:59 schrieb Carl Eugen Hoyos: > > Reindl Harald thelounge.net> writes: > > > >> Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos: > >>> John Pompeii ffmpeg.org> writes: > >>> > --enable-bzlib > --enable-iconv > --enable-lzma > --enable-zlib > >>> > >>> These options have no effect, they do not do > >>> what you seem to believe they do. I suggest > >>> you remove them > >> > >> since you always suggest to remove them *why* do > >> the exist at all in ./configure --help and not > >> only their counterpart --disable-xx? > > > > [quote] > >--disable-bzlib disable bzlib [autodetect] > >--disable-zlib disable zlib [autodetect] > >--disable-iconv disable iconv [autodetect] > >--disable-lzma disable lzma [autodetect] > > [/quote] > > > > ??? > > typically configure scripts warn about unkonwn params > ffmpeg don't FFmpeg configure does not warn about unknown parameters, it errors out, just try "./configure --enable-foo". The parameters above are not unknown, they are useful for debugging but not for users, this is why they are not listed in configure --help (that was what you both denied and requested, no?). The options you use in your configure line are to some degree useless, to some degree they hurt performance for no gain and some (as --enable-zlib) do not work the way you (apparently) think they work: They simply have no effect. Since the configure line is often needed to debug issues it is very useful to remove all unneeded options, especially those that may produce issues in the future because they never had the meaning you think they have. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Am 22.01.2016 um 01:16 schrieb Carl Eugen Hoyos: Reindl Harald thelounge.net> writes: Am 22.01.2016 um 00:59 schrieb Carl Eugen Hoyos: Reindl Harald thelounge.net> writes: Am 22.01.2016 um 00:41 schrieb Carl Eugen Hoyos: John Pompeii ffmpeg.org> writes: --enable-bzlib --enable-iconv --enable-lzma --enable-zlib These options have no effect, they do not do what you seem to believe they do. I suggest you remove them since you always suggest to remove them *why* do the exist at all in ./configure --help and not only their counterpart --disable-xx? [quote] --disable-bzlib disable bzlib [autodetect] --disable-zlib disable zlib [autodetect] --disable-iconv disable iconv [autodetect] --disable-lzma disable lzma [autodetect] [/quote] ??? typically configure scripts warn about unkonwn params ffmpeg don't FFmpeg configure does not warn about unknown parameters, it errors out, just try "./configure --enable-foo". The parameters above are not unknown, they are useful for debugging but not for users, this is why they are not listed in configure --help (that was what you both denied and requested, no?). The options you use in your configure line are to some degree useless, to some degree they hurt performance for no gain and some (as --enable-zlib) do not work the way you (apparently) think they work: They simply have no effect. Since the configure line is often needed to debug issues it is very useful to remove all unneeded options, especially those that may produce issues in the future because they never had the meaning you think they have when "they simple have no effect" how can they "be useful" for debugging? which ones hurt performance for no gain? signature.asc Description: OpenPGP digital signature ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Reindl Harald thelounge.net> writes: > when "they simple have no effect" how can they > "be useful" for debugging? They have no effect in your configure line and they have no effect in the configure line that was posted in this thread. There are configure lines (that are hardly useful for users but can be very useful when debugging as a developer) in which they have an effect. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Thanks Carl for the heads up. I am fairly new to ffmpeg in general and have a need to add a new protocol that supports reading video files that our application encrypts usinga aes-ctr algorythm. So not knowing any better, I grabbed the build flags that are displayed when running the latest ffmpeg from the binary distribution. I have eliminated about half of those already but I wasn't sure about these. I didn't add them becauseI thought I needed them, I was just trying to replicate the distribution version. thanks,--john From: Carl Eugen Hoyos <ceho...@ag.or.at> To: ffmpeg-user@ffmpeg.org Sent: Thursday, January 21, 2016 6:41 PM Subject: Re: [FFmpeg-user] How to build for static ffmpeg executable John Pompeii ffmpeg.org> writes: > --enable-bzlib > --enable-iconv > --enable-lzma > --enable-zlib These options have no effect, they do not do what you seem to believe they do. I suggest you remove them. Carl Eugen ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
Thanks Glen,These flags are the default. I build with them anyway and got the same result. the ff* libs are build as static libs but the ffmpeg excutable is linked w/the shared libs for the external libs and runtimes. here's my cmd line for configure: ./configure --prefix=/mingw64/share/ffmpeg/rel --disable-ffplay --disable-ffserver --disable-doc --enable-gpl --enable-version3 --disable-w32threads --enable-static --disable-shared --enable-avisynth --enable-fontconfig --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg --enable-libopus --enable-libtheora --enable-libvo-aacenc --enable-libvorbis --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 --enable-libxvid --enable-libzimg From: G A <glen_alex...@hotmail.com> To: FFmpeg user questions <ffmpeg-user@ffmpeg.org> Sent: Thursday, January 21, 2016 2:12 PM Subject: Re: [FFmpeg-user] How to build for static ffmpeg executable specify -—disable-shared —enable-static Sent from somewhere in … The Twilight Zone > On Jan 21, 2016, at 06:52, John Pompeii <lksm6-at-yahoo@ffmpeg.org> wrote: > > > > > Hi, > I am building ffmpeg.exe and ffprobe.exe on 64 bit windows (7) using > MSYS2/MINGW64. I've resolved all the dependent libraries and got a build and > it does appear to run just fine as a 64 windows app. This issue that I have > is that its linking the external libraries as dlls instead of static libs. I > build the ffmpeg libs as static and assumed that the build would statically > link all libraries, but not so. > > Can someone let me know how to build version of ffmpeg.exe that doesn't > require dlls for the dependent libraries (including the compiler and gnu > runtimes) for windows? In the binary packages distributed by ffmpeg, these > dependent dlls are not there for the windows versions, regardless of a static > or shared lib build, so I'm missing something in the way I'm configuring the > build. > > thanks,--john > > The configure command line I'm using is:./configure > --prefix=/mingw64/share/ffmpeg/rel --disable-ffplay --disable-ffserver > --disable-doc --enable-gpl --enable-version3 --disable-w32threads > --enable-avisynth --enable-bzlib --enable-fontconfig --enable-iconv > --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg > --enable-libopus --enable-libtheora --enable-libvo-aacenc --enable-libvorbis > --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 > --enable-libzimg --enable-lzma --enable-zlib > > The DLL's required to load and run ffmpeg.exe are:libbz2-1.dll > libfontconfig-1.dll > libfreetype-6.dll > libgcc_s_seh-1.dll > libglib-2.0-0.dll > libharfbuzz-0.dll > libiconv-2.dll > libintl-8.dll > liblzma-5.dll > libopenjpeg-5.dll > libstdc++-6.dll > libtheoradec-1.dll > libtheoraenc-1.dll > libwavpack-1.dll > libwinpthread-1.dll > libx265.dll > libzimg-2.dll > SDL.dll > > It would seem that some libs (such as x264) are linking statically > > > > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
specify -—disable-shared —enable-static Sent from somewhere in … The Twilight Zone > On Jan 21, 2016, at 06:52, John Pompeiiwrote: > > > > > Hi, > I am building ffmpeg.exe and ffprobe.exe on 64 bit windows (7) using > MSYS2/MINGW64. I've resolved all the dependent libraries and got a build and > it does appear to run just fine as a 64 windows app. This issue that I have > is that its linking the external libraries as dlls instead of static libs. I > build the ffmpeg libs as static and assumed that the build would statically > link all libraries, but not so. > > Can someone let me know how to build version of ffmpeg.exe that doesn't > require dlls for the dependent libraries (including the compiler and gnu > runtimes) for windows? In the binary packages distributed by ffmpeg, these > dependent dlls are not there for the windows versions, regardless of a static > or shared lib build, so I'm missing something in the way I'm configuring the > build. > > thanks,--john > > The configure command line I'm using is:./configure > --prefix=/mingw64/share/ffmpeg/rel --disable-ffplay --disable-ffserver > --disable-doc --enable-gpl --enable-version3 --disable-w32threads > --enable-avisynth --enable-bzlib --enable-fontconfig --enable-iconv > --enable-libfreetype --enable-libmp3lame --enable-libopenjpeg > --enable-libopus --enable-libtheora --enable-libvo-aacenc --enable-libvorbis > --enable-libvpx --enable-libwavpack --enable-libx264 --enable-libx265 > --enable-libzimg --enable-lzma --enable-zlib > > The DLL's required to load and run ffmpeg.exe are:libbz2-1.dll > libfontconfig-1.dll > libfreetype-6.dll > libgcc_s_seh-1.dll > libglib-2.0-0.dll > libharfbuzz-0.dll > libiconv-2.dll > libintl-8.dll > liblzma-5.dll > libopenjpeg-5.dll > libstdc++-6.dll > libtheoradec-1.dll > libtheoraenc-1.dll > libwavpack-1.dll > libwinpthread-1.dll > libx265.dll > libzimg-2.dll > SDL.dll > > It would seem that some libs (such as x264) are linking statically > > > > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
of course it is enough. it works on unix/osx, i build ffmpeg with 40 plugins from the repo every few days and these flags work. Sent from somewhere in … The Twilight Zone > On Jan 21, 2016, at 11:22, Reindl Haraldwrote: > > > > Am 21.01.2016 um 20:12 schrieb G A: >> specify -—disable-shared —enable-static > > that's not enough if your shared libraries are just dll/so files > they *all* need to be built static > > ___ > ffmpeg-user mailing list > ffmpeg-user@ffmpeg.org > http://ffmpeg.org/mailman/listinfo/ffmpeg-user ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user
Re: [FFmpeg-user] How to build for static ffmpeg executable
On Thu, Jan 21, 2016 at 11:27:54 -0800, G A wrote: > of course it is enough. it works on unix/osx, i build ffmpeg with 40 > plugins from the repo every few days and these flags work. That's nonsense. Even though we're talking Windows here (for the original poster at least), that's not valid on the named platforms. And BTW ffmpeg doesn't support anything which resembles plugins. Moritz ___ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org http://ffmpeg.org/mailman/listinfo/ffmpeg-user