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