On Wed, Mar 13, 2002 at 02:17:43PM +0100, Bert Freudenberg wrote:
> On Wed, 13 Mar 2002, Kevin Fisher wrote:
> 
> > Hi Lex:
> > 
> > I initially generate my plugin via VMMaker, but my subsequent hacking
> > on my plugins use the simple 'PluginName translate' facility to generate
> > updated C files for my plugin.
> > 
> > If I use VMMaker each time, will this magically take care of the library
> > problems?
> 
> There is no magic ;-)

Drat!

> 
> > Specifically, my plugin uses libglib and libxmms.  When I attempt
> > to use it, it complains that it cannot find references to functions  found
> > in libglib and libxmms.  If I link the VM executable to -lglib -lxmms,
> > the problem goes away, however. 
> 
> 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?

[snip]