Plugin creation question...

Kevin Fisher kgf at golden.net
Wed Mar 13 17:11:06 UTC 2002


On Wed, Mar 13, 2002 at 08:24:33AM -0800, Tim Rowledge wrote:
> In message <20020313081109.C27579 at blackwolf.golden.net>
>           Kevin Fisher <kgf at golden.net> wrote:
> 
> > 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.
> That's ok, but since VMMaker will put your file(s) in the proper
> place(s) each time, why not use it and save having to move them? Just
> keep a VMMakerTool open, with your plugin in the 'external' list. Every
> time you edit the code use the menu to generate just that plugin. Then
> go to your console and do make, make update, whatever. If you have
> already created and loaded the plugin, you can unload it with <Smalltalk
> unloadModule: 'moduleName'> ready to try out thenew version. Andreas &
> I did a lot of that when originally dping the VM modularization stuff.
> It should still work ok!


To be honest, I hadn't even thought of it until it was mentioned here today.
:)  I'll be doing this from now on, to be sure.  It makes me smile 
that my little 'beginners plugin' is already recognized and used by
VMMaker.

Again, I was pretty much going 'by the book' (meaning the NuBlue book), which
just shows "PluginName translate" as a working example...

> 
> > 
> > If I use VMMaker each time, will this magically take care of the library
> > problems?
> There's nothing currently in VMMaker to handle this. As a guess, (those
> of you that know about unix libraries might have useful thougts here) we
> could add something to either the plugin class itself or to the platform
> specific subclass of VMMaker to add these words to some makefile
> fragment. For now though, just add them to the makefile or use the local
> mkFrag stuff Lex added.

Yes, this sounds like what I need to do.

> 
>  Bertf said-
> >>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.

[snip]




More information about the Squeak-dev mailing list