[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

509.0. "Converting X11 programs" by INFACT::DATZMAN (Indianapolis Field Applications Center) Thu Mar 30 1989 16:05

    How much work is involved in converting X11 programs from other
    systems(Sun, Apollo, HP, whoever) to run under DECwindows VMS?
    
    Dick

T.RTitleUserPersonal
Name
DateLines
509.1GVRIEL::SCHOELLERWho's on first?Thu Mar 30 1989 17:337
I don't know about officially, but unofficially there has been quite a few
programs off of the X11R3 release ported to run on VMS.  Generally these things
run fine on Ultrix it only VMS that causes problems.  I am not sure if this is
the sort of thing you are looking for though.

Dick

509.2Specific modifications, please..INFACT::DATZMANIndianapolis Field Applications CenterThu Mar 30 1989 21:395
    What I was interested in, is generally the types of modifications
    that are necessary for these programs to compile and run on VMS.
    
    Dick

509.3UFP::MURPHYThe SUN just set!Fri Mar 31 1989 00:2419
    In my experience, most ports of generic Unix-based X programs to VMS
    require little effort in the X code; a simple
    	$ DEFINE SYS SYS$LIBRARY
    	$ DEFINE X11 DECW$INCLUDE
    allows most to compile without change. The rest of the porting effort
    is spent in getting the OS-specific stuff out - that is, application
    calls to routines that aren't in the VMS C Run-time library need to be
    hacked around. The biggest problem is code that does select calls on
    the X connection. As an example, the HP window manager and toolkit
    (some 140+ files, 93000+ lines of source code) ported to VMS with
    three late nights of hacking and maybe 10 instances of VMS-specific
    changes to make it work. That's what happens when you start with
    reasonably portable code to start with.
    
    Now, on the other hand, your question is difficult at best to answer
    for the general case; treat it as a question of how difficult is *any*
    utility to port to VMS, not how a X-windows utility can be ported.
    	-Rick

509.4ThanksINFACT::DATZMANIndianapolis Field Applications CenterFri Mar 31 1989 10:174
    Thanks.  This is helpful.
    
    Dick

509.5getoptIAGO::SCHOELLERWho's on first?Fri Mar 31 1989 14:327
One of the more common porting problems in that the applications call getopt()
to parse command line options.  This is not supplied with VAXC.  Fortunately,
many of the already ported applications have getopt in them.  A few provide
it as a separate source file so it can be shared around.

Dick

509.6index, bcopyXWORLD::STUARTHi! I ate Cleveland. I ate Tokyo, too.Fri Mar 31 1989 14:4311
a lot of applications that come over the usenet comp.sources.x channel use the
'index' and 'bcopy' functions, which correspond to 'strchr' and 'memcpy' in 
VAXC. a simple 

#define index strchr
#define bcopy memcpy

usually does the trick.

s

509.7free must be changed to XFreeCVG::PETTENGILLmulpTue Apr 04 1989 20:474
I've found a number of X11R3 programs mysteriously ACCVIO on VMS due to calls to
free.  Frequently the ACCVIO seems to be totally unrelated to any thing.
These calls need to be changed to the appropriate Xlib call, usually XFree.