[vlc-devel] --disable-plugins does not link statically anymore on iPaq.

Jean-Paul Saman jpsaman at wxs.nl
Sat Jan 25 16:27:11 CET 2003

Since commit of version 1.123 of configure.ac.in --disable-plugins has 
no effect anymore. It still builds modules as *.so, so the difference 
between --enable-plugins and --disable-plugins is non-existing.

The commit comment was:
  ./configure.ac.in: fixed multiple static link issues with anal linkers.

I do not know what problems was fixed with this, but it does not do what 
is expected when using the arm-linux toolchain. If I use a 
--with-ffmpeg-tree= or --with-mad-tree, then statically linking is 
expected by me.

In my trees there are usually shared and static libraries and I want to 
have a choice against which the application is being build. 
--enable-plugins should default to shared libs and --disable-plugins 
should default to static libs.

Could we add a "-static" as linking options for the linking stage to 
instruct every compiler to use static libraries when --disable-plugins 
are used? And "--shared" when --enable-plugins is used! In this way the 
*old* behaviour is restored! Please comment

Jean-Paul Saman.

This is the vlc-devel mailing-list, see http://www.videolan.org/vlc/
To unsubscribe, please read http://developers.videolan.org/lists.html
If you are in trouble, please contact <postmaster at videolan.org>

More information about the vlc-devel mailing list