Re: Removing '--enable/disable-shared/static' options from configure script

[Asfand Yar Qazi]

Ralf Wildenhues wrote:
> Hello,
>
> * Asfand Yar Qazi wrote on Thu, Feb 09, 2006 at 10:42:38PM CET:
>
> > How do I remove the --enable-shared, --disable-shared, --enable-static and 
> > --disable-static options from being displayed in the help or being used in 
> > configuration?
>
>
> These are added by Libtool.  If you don't use it, they should not
> appear, so removing AC_PROG_LIBTOOL should help.
>
> If you would like to use Libtool but do not want those options: as far
> as I know, that is not supported at the moment.  Why would you want to
> disable this then?
>
> Cheers,
> Ralf

I'm basically asking on behalf of a project that does not support static 
linkage, only dynamic linkage.  When doing static linkage, it compiles the 
dynamic libraries into static ones alright, but the project is designed to 
dynamically load (using dlopen) libraries in at run-time, and therefore the 
applications that use the library still ask for the dymamic library.

It's kind of wierd - they need libtool for the dynamic linking, and don't 
support static linking (the programs alway ask for the dynamic libraries which 
they expect to load in at runtime).

Another way: is there a macro that removes arguments given to 'configure', 
that can be used to not allow the enable-static or disable-dynamic arguments 
through.