On Wed, 13 Mar 2002, Lex Spoon wrote:

> Bert Freudenberg <bert at isg.cs.uni-magdeburg.de> wrote:
> > On Wed, 13 Mar 2002, Kevin Fisher wrote:
> > 
> > > > Sure. This is the Right Thing if the plugin is compiled internally. If it 
> > > > is made external, however, the plugin itself shoulf be linked to that 
> > > > libs, not the VM.
> > > 
> > > How do you do this externally, then?  Is there a way to do it from Slang
> > > (so that it's automatically generated the "right way"), or do I have
> > > to manually hack up the Makefile after VMMaker generates everything?
> > 
> > You can put a mkMakeRules script into your plugin directory. For a rather 
> > complicated example, see unix/plugins/Mpeg3Plugin/mkMakeRules
> > 
> > It is called as 
> > 	$unixdir/plugins/$plugin/mkMakeRules $topdir internal
> > or 
> > 	$unixdir/plugins/$plugin/mkMakeRules $topdir external
> > from the script
> > 	platforms/unix/misc/util/mkMake ...
> > 
> 
> Yes, that would be the best way.
> 
> Unfortunately there is a problem.  libtool, the nice generic
> library-generating tool that is used to build things right now, doesn't
> like to link shared libraries against other libraries, even when the
> platform will allow it.  I don't know a good solution for this; go bang
> on the libtool people??  In the meantime I guess hacking Makefile.in is
> the easiest way to move forward.
> 
> (Or maybe newer libtools even fix the problem; I certainly haven't
> checked!)

I think this was fixed in libtool 1.4:
See http://sources.redhat.com/autobook/autobook/autobook_77.html

-- Bert