Xref: utzoo comp.graphics:15017 comp.windows.open-look:270
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!umich!gumby!wmu-coyote!john
From: john@sol.cs.wmich.edu (John Kapenga)
Newsgroups: comp.graphics,comp.windows.open-look
Subject: SRGP and openwindows ?
Keywords: SGRP, openwindows, cc, gcc
Message-ID: <1990Dec15.170428.8738@sol.cs.wmich.edu>
Date: 15 Dec 90 17:04:28 GMT
Organization: Western Michigan Univ. Comp. Sci. Dept.
Lines: 37


I have been trying to get the SGRP library (Foley et al) to compile
correctly under SUNs stock openwindows 2.0 on sparcs. SGRP was compiled
with gcc 1.37.1 and flags effecting gcc to cc linkage were tried.
Such as
#The following flags must be defined for UNIX/X11 implementations
CPPFLAGS = -DX11 -DUNIX -I/usr/openwin/include
#Very important!  The first flag (struct-return) makes it safe to link
#  gcc objects with cc objects.
GCCFLAGS = -fpcc-struct-return
# Special Flags that are tried in various combinations
GSPECIAL = -static -fwritable-strings -mno-epilogue -traditional
Compilations give no warnings and link with SUNs X libraries fine.

What happens is that some examples which use output only function work
correctly (invoking them from a shelltool under openwindows). All routines
which request input seem to hang, resulting in 100% CPU usage until the 
object is killed. It seems impossible to bind the keyboard to the newly
opened graphics window. 

This was on a SUN 4/110, Sparcstation 1+ and an IPC. And SGRP was ftped
from brown in early December.

Options I see:
	use X libraries compiled with gcc and ANSI headers
		(this is recommended in the SGRP docs and likely will work,
		but requires a fair amount of extra disk space),
	wait for SUN to release an ANSI C compiler (wait is the operational
		term),
	de ANSI sgrp (automated, but undesirable),
	go in to hack/debug mode.

Please mail any suggestions. If there is interest (and it works)
I will summerize.

john      
john@sol.cs.wmich.edu