brian@moci.UUCP (Brian R. Daleiden) (07/19/90)
Hi, One of our multi-platform products(UN*X, VMS, DOS, Macintosh) was written under SCO UNIX/XENIX. I am unfamiliar with Interactive's flavor. I am looking at support of our product on this OS. Can somebody fill me in on the differences between the two from a users view as well as any porting gotchas that I might run into in the process. Please send responses via email if possible and I will summarize if interest warrents. Thanks for any and all help! -Bri -- Brian Daleiden (414) 789-7550 ICOM Inc. "Innovative Software Solutions" (414) 321-8000 2424 S. 102nd St., Milwaukee WI 53214 ..!uwm.edu!moci!brian
cpcahil@virtech.uucp (Conor P. Cahill) (07/19/90)
In article <189@moci.UUCP> brian@moci.UUCP (Brian R. Daleiden) writes: > One of our multi-platform products(UN*X, VMS, DOS, Macintosh) was >written under SCO UNIX/XENIX. I am unfamiliar with Interactive's >flavor. I am looking at support of our product on this OS. Can somebody >fill me in on the differences between the two from a users view as well >as any porting gotchas that I might run into in the process. If you started with SCO's cc compiler, then you should be ok in porting the stuff to Interactive. You usually have much more problems going the other way. As to porting problems, as long as you don't do any of the following you should be ok: 1. direct display control 2. direct keyboard control 3. work in the kernel (i.e. device drivers, etc) 4. do things within the spooling system (as opposed to just lp'ing the file) At this point you have both binary and source code compatibility, so you could just release the same binaries on the other system. The only other exclusion for binaries is that you don't release a product that is supposed to be recompiled/linked to, since the compiler tools on xenix don't understand interactive objects and vice-versa. -- Conor P. Cahill (703)430-9247 Virtual Technologies, Inc., uunet!virtech!cpcahil 46030 Manekin Plaza, Suite 160 Sterling, VA 22170