[FFmpeg-trac] #1968(build system:new): ./configure --enable-shared --enable-static behavior odd.

[FFmpeg]

#1968: ./configure --enable-shared --enable-static behavior odd.
-------------------------------------+-------------------------------------
             Reporter:  rogerdpack   |                    Owner:
                 Type:  defect       |                   Status:  new
             Priority:  normal       |                Component:  build
              Version:  unspecified  |  system
             Keywords:               |               Resolution:
             Blocking:               |               Blocked By:
Analyzed by developer:  0            |  Reproduced by developer:  0
-------------------------------------+-------------------------------------

Comment (by cehoyos):

 Replying to [comment:4 rogerdpack]:
 > The confusion comes when you do both of them together.  It's like it
 must decide "which one" to use for building ffmpeg.exe (large, or small?)

 Please understand that both "--enable-shared" and "--enable-static" do not
 directly influence if ffmpeg (the executable) is linked statically or
 dynamically (or is, in your words, "large or small"), test for example
 "./configure --disable-static --enable-shared && make ffmpeg; ./configure
 --enable-static --disable-shared && make ffmpeg" and you will see that
 only the linker (that is not part of FFmpeg) decides which library files
 to use. (Even if I am wrong and linkers must use the dynamic libraries to
 conform to some specification that does not change my argument that this
 in no way indicates a bug in FFmpeg.)

 Allow me to repeat the question:
 If you configure with "--enable-shared --enable-static" are the static
 archives - libavutil/libavutil.a, libavcodec/libavcodec.a,
 libavformat/libavformat.a, ... - built or not?

-- 
Ticket URL: <https://ffmpeg.org/trac/ffmpeg/ticket/1968#comment:6>
FFmpeg <http://ffmpeg.org>
FFmpeg issue tracker