[comp.windows.x] Questions on setup on ISC's X11 Dev

paine@fungus.dec.com (Willy Paine) (12/30/89)

I am using X-windows and DECwindows on the job for long time and I do
some X11 dev at work with DEC.  Recently I installed X11 in Interactive
386/ix 2.0.2 and I am trying to port some of my X11 goodies into ISC
environment.   I want to use awm window manager instead of uwm and I got
sources code from usenet.  Also want to port xgif.  I could not compile
because header files (.../X11/include/Vox.h) could not find other header 
files and also I am getting many unresolved external from ISC's own X11
library.  

My questions are:

Should I make separate header file to resolve X11 header problem or
modifying inside X11 header files (Vos.h etc)?

How can I overcome the problem with many unresolved external from ISC's
own X11 library for my future X11 development?

What is your advice on setting up ICS X11 Development environment before
I bring many sources from my work?  Most of sources are from usenet and
MIT.

Thank in advance.. Happy Holiday!!

willy

................................................................
.   Willy Paine                      BBS/FAX +1-206-822-4615   .
.   willyp@seaeast.WA.COM            FidoNet 1:343/15          .
.   uunet!nwnexus!seaeast!willyp     fungus.enet.dec.com!paine . 
................................................................
.   It takes less time to do a thing right than to explain     .
.   why you did it wrong  - Longfellow.                        .
................................................................

jackv@turnkey.gryphon.COM (Jack F. Vogel) (01/02/90)

In article <8912291842.AA12534@decwrl.dec.com> paine@fungus.dec.com (Willy Paine) writes:
 
>My questions are:
 
>Should I make separate header file to resolve X11 header problem or
>modifying inside X11 header files (Vos.h etc)?
 
>How can I overcome the problem with many unresolved external from ISC's
>own X11 library for my future X11 development?
 
How is anyone supposed to help you when you leave out essential details like
what the unresolved externals were or what the header files that were not
found were????

All I can say without these details is that I have been using the ISC X
development package without these problems. My guess is that the unresolved
externals one might get would come from the BSD networking library stuff,
to resolve that include -linet in your linker flags (this assumes you have
/usr/lib/libinet.a installed, I forget what package it is in). The other
type of problem I have had involved some client code that used header files
normally in the libX source directory that ISC did not distribute in
<X11/*.h>. I don't recall what they were but if you have the X distribution
around it shouldn't be too hard to figure out.

Good Luck,
--
Jack F. Vogel			jackv@seas.ucla.edu
AIX Technical Support	              - or -
Locus Computing Corp.		jackv@ifs.umich.edu

erc@pai.UUCP (Eric Johnson) (01/02/90)

In article <6405@turnkey.gryphon.COM>, jackv@turnkey.gryphon.COM (Jack F. Vogel) writes:
> In article <8912291842.AA12534@decwrl.dec.com> paine@fungus.dec.com (Willy Paine) writes:
>  
> >My questions are:
>  
> >How can I overcome the problem with many unresolved external from ISC's
> >own X11 library for my future X11 development?
> > ...
>  
> All I can say without these details is that I have been using the ISC X
> development package without these problems. My guess is that the unresolved
> externals one might get would come from the BSD networking library stuff,
> to resolve that include -linet in your linker flags (this assumes you have
> /usr/lib/libinet.a installed, I forget what package it is in). The other
> type of problem I have had involved some client code that used header files
> normally in the libX source directory that ISC did not distribute in
> <X11/*.h>. I don't recall what they were but if you have the X distribution
> around it shouldn't be too hard to figure out.
> 
> ...
> Jack F. Vogel			jackv@seas.ucla.edu
> AIX Technical Support	              - or -
> Locus Computing Corp.		jackv@ifs.umich.edu


If you are using Interactive's 386/ix UNIX and have both X11 and
TCP/IP networking developer systems installed, you will need
to link in the "inet" library after the X11 library.  For example,

cc -o xhello xhello.c -lX11 -linet

Interactive apparenty uses shared memory for Inter-Process Communication
if you do not have networking installed, and Berkeley-style sockets
for IPC if networking is installed.

This was rather annoying to figure out.  But, their version of X does seem
to work (not as fast as the SPARCStation, but pretty good for a PC
clone).


Hope this helps,

-Eric


-- 
Eric F. Johnson, Boulware Technologies, Inc. 
415 W. Travelers Trail, Burnsville, MN 55337 USA.  Phone: +1 612-894-0313. 
erc@pai.mn.org    - or -   bungia!pai!erc
(We have a very dumb mailer, so please send a bang-!-style return address.)