daniel@island.uu.net ((Dan Smith - "measure twice, cut once")) (01/09/90)
Let's discuss for a moment "how to get all of this to coexist?" :-)
I'm wondering how people out there have set up R3 and R4, with
and without Motif (libs, includes), all on the same machine. I'm referring
to things like /usr/lib/libX11.a, /usr/lib/libX11_motif.a, Motif includes
vs Standard R3, /usr/bin/X11 vs what? (/usr/bin/X11R4?) I sure wish there
were variant links on Suns (something I like about Apollos!).
There's got to be a few good ways - I'd like to hear them. The less
confusing I can make things for programmers/other users here the better. My
thoughts lean towards using environment variables and symlinks in (hopefully!)
straightforward ways.
Oh, and just to make things more interesting...X{NeWS,View}, Open*
as well :-)
Thanks in advance for input!
dan
--
dansmith@well.sf.ca.us daniel@island.uu.net unicom!daniel@pacbell.com
ph: (415) 332 3278 (h), 491 1000 (w) disclaimer: Island's coffee was laced :-)abair@turbinia.oakhill.uucp (Alan Bair) (01/12/90)
I put the includes, libs, binaries, etc in /usr/local/...., so I have always made changes to the site.def to relocate this files. When I also wanted to run Motif and XView along side X11, I just made changes in their site.def files to put the code in places like /usr/local/lib/[Motif,XView]. I did this for the includes, and binaries on Motif and XView, but only includes and binaries on X11. All three use the use the same /usr/local/lib/X11 for fonts, app_defualts, etc. Its painfull to setup, but once its in place its easy to maintain. As far as the users are concerned, I have a set of scripts to setup the appropriate environment based on whether they want to run X11, Motif or XView. They already have to add "-L..." and "-l...." to the cc command, so they just set it to what they are using for the program they are working on. It would be nice to have the variant links, then you could just set an environment variable and everything would be ready to use. -- Alan Bair SPS CAD Logic Simulation & Test Motorola, Inc. Austin, Texas ...!cs.utexas.edu!oakhill!turbinia!abair
barnett@grymoire.crd.ge.com (Bruce Barnett) (01/13/90)
In article <ABAIR.90Jan11144200@turbinia.oakhill.uucp> abair@turbinia.oakhill.uucp (Alan Bair) writes: |I put the includes, libs, binaries, etc in /usr/local/...., so I |have always made changes to the site.def to relocate this files. I had a different strategy that others might be interested in. We have users experimenting with different version of X on diskless clients. I created a new directory (/usr/common/X) that had symboslic links pointing to another difectory. I then created symbolic links in /usr/bin/X11, /usr/include/X etc. that pointed to the right spot in /usr/common/X For most users - everything was fine. If I wanted to change the "default" version of X, I change the links in /usr/common/X. If it was I proble, I could change it back. For the user whose workstation needs a different release, I would mount a different directory on top of /usr/common/X. -- Bruce G. Barnett barnett@crd.ge.com uunet!crdgw1!barnett