On Wed, Nov 12, 2003 at 08:22:18PM +0000, Mike Roberts wrote:
> Osdfn Wed, Nov 12, 2003 at 11:46:28AM +0100, Alexander Lazarevic wrote:
> Content-Description: signed data
> > Am Mittwoch, 12. November 2003 01:50 schrieb Mike Roberts:
> > > I've quickly checked that if you make the plugin external then it all
> > > builds.
> > 
> > Then this is the way to go. You might want to make the following plugins 
> > external too (only if you plan to build them of course :).
> 
> Thanks, I do realise now that I only tried this right at the end, after I had composed most of the email.  It should have dawned on me sooner!  I am curious however as the documentation talks about both internal and external linkage.
> 

I normally build OSProcessPlugin and XDisplayControlPlugin as external, so I missed this
problem. The above advice is right, but just for information:

OSProcessPlugin has a left over reference to an unnecessary X display function. I'll
get rid of this the next time I put out an update, and then it should build OK either
externally or internally (but I still would recommend external).

XDisplayControlPlugin must be built externally, because it refers to the global
variable 'displayName' in the vm-display-X11.so shared library. The unix VM is
now set up to have the vm-display-whatever modules built externally, and
XDisplayControlPlugin must also be external in order for this to work.

Dave