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

[Asfand Yar Qazi]

Ralf Wildenhues wrote:

<snip>

> > 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).
>
>
> Shameless plug: if you already use Libtool for dynamic linking, why not
> also use libltdl for portable module loading?  libltdl even allows you
> (through preloading) to use a module emulation that works on systems
> without any sort of dynamic linking (or in the disable-shared case).

I'm posting on behalf of the Ogre project (www.ogre3d.org) and they've already 
got their dynamic module loading system in place, I don't think they want to 
change.  I can't agree with their 'load everything dynamically' setup, but I 
just want to stop people compiling their project statically (like the build 
system allows) and then not be useable (like it ends up.)

> > 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.
>
>
> Not that I know of.  The best I could think of off-hand would be to
> check at configure time that it has not been used.

So should they run a script that patches their configure script after it is 
generated, or can some shell programming be placed in their configure.in 
script that will end up in the configure script in the right place?


Thanks,
       Asfand Yar