[comp.windows.x] Athena VendorShell and Shared Libraries?

taylort@decus.com.au (Trevor Taylor) (02/26/91)

I've come across a problem with the Athena widgets in a VMS
environment: They assume that the Xaw VendorShell will be used 
so that it can register some resource converters.

On VMS, Xlib and Xt are provided as shareable libraries, i.e.
all the Xt routines and the basic widgets (including VendorShell)
are pre-linked. Therefore, the Xaw VendorShell is never pulled
in from the object library because the global is already satisfied.

I can of course link in vendor.obj explicitly and put up with 
multiply defined global errors when I link, but it begs the question: 
Is there any other mechanism for one-off initialisation of a widget 
set that is relatively invisible to the programmer? 

(In other words, having to call an explicit initialisation routine 
would mean changing all the existing Xaw clients, and I don't want 
to do that!)

/*--------------------------------------------------------------------*/
/*    Trevor Taylor               E-Mail: TaylorT@decus.com.au        */
/*    P.O. Box 155                        T.Taylor@praxa.com.au       */
/*    Aspley 4034                 Phone:  +(61) 7 369-8100            */
/*    Australia                   Fax:    +(61) 7 369-0722            */
/*--------------------------------------------------------------------*/