Xref: utzoo comp.sys.hp:9258 alt.toolkits.xview:204
Path: utzoo!utgpu!cs.utexas.edu!sun-barr!olivea!uunet!mcsun!ukc!mucs!liv-cs!kjc
From: kjc@and.cs.liv.ac.uk
Newsgroups: comp.sys.hp,alt.toolkits.xview
Subject: Re: XView on HP-UX
Message-ID: <1991Jun5.141128.86@and.cs.liv.ac.uk>
Date: 5 Jun 91 14:11:28 GMT
Organization: Computer Science, Liverpool University
Lines: 64

Re: XView on HPs

The documentation with XView2 suggests that SUN are porting XView to the HP 
platform themselves so you might consider waiting until they release that
version.

I got "most" of XView2 working on a hp9k300 machine (running HPUX 7.0 and 
MIT X11R4) - unfortunately I ran out of filestore before I could complete the
port. I can't even resurrect the files to see what changes I made ...  If only 
someone would loan me a disk .... (sigh). From what I remember it was NEAT.

If you intend to do the port heres some pointers to help you (if my memory 
serves me) ...

1. Most of the modifications required are the usual converting BSD to 
   SysV stuff - different header files, alternative function calls etc.

2. You need to take a high level decision on what CFLAGS to set. The main one
   to consider is whether to use -DSVR4 or not. I originally defined this flag
   in order to get the correct header files; however a side-effect of setting 
   this flag is that a lot of the SIGNAL and SOCKET stuff will break. With
   hindsight I think its better not to define SVR4 and manually fix the 
   "#include <...>" lines by hand.

3. You need to convert BSD tty(4) routines to the ATT termio(7) equivalents.

4. XView makes extensive use of enums and these cause problems when they are 
   used as part of the "expression" in a switch statement. This was a difficult 
   "bug" to find - even running with the debugger. Essentially you have to 
   cast ALL such expressions to int (and theres a lot of them!) ie ...

   enum abc ; 			enum abc ;
   .				.	
   .				.
   switch ( abc ) 	-->	switch ( (int)abc )
   { 				{
      case xyz:			   case xyz:
      .				   .
      .				   .

   I haven't decided if this is sloppy coding (on SUNs part) or a genuine bug
   with the HP C compiler - I can't recreate the problem with a small program.
   
You should be able to get clock, olwm, textedit and cmdtool to work (in a 
fashion). The only outstanding problem I had (I think) concerned the mapping 
of function keys on the SUN and their equivalents on the HP ; basically the
SUN has many, many more function keys which are used by XView.

Hope the above helps - don't hestitate to get in contact if you need more 
info.

Kenneth Chan

postal: Kenneth Chan
        Computer Science Dept.
        University Of Liverpool
        PO Box 147
        Liverpool
        L69 3BX

email:  kjc@uk.ac.liv.cs.and 

PS: can't "reply" to you direct mailer problems - so sending this message 
    to comp.sys.hp and alt.toolkits.xview