Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!usc!apple!sun-barr!lll-winken!gauss.llnl.gov!casey
From: casey@gauss.llnl.gov (Casey Leedom)
Newsgroups: comp.windows.x
Subject: Re: difficulty installing in other than /usr/[bin,lib,include]/X11
Message-ID: <39283@lll-winken.LLNL.GOV>
Date: 23 Nov 89 00:42:26 GMT
References: <29336@shemp.CS.UCLA.EDU> <3294@convex.UUCP>
Sender: usenet@lll-winken.LLNL.GOV
Reply-To: casey@gauss.llnl.gov (Casey Leedom)
Organization: Lawrence Livermore National Laboratory
Lines: 47

| From: datri@convex.COM (Anthony A. Datri)
| 
| >I tried to make X to sit in /n/color/share/usr/bin/X11R3, with
| 
| I'd suggest just making /usr/bin/X11, /usr/lib/X11, and /usr/include/X11
| links to directories where you want things to really be.

  This isn't necessary in the least.  We've been running with X11.3
installed under /usr/local/{bin,lib,include} for nearly a year now with
no problems.  Two csh aliases will help you on Berkeley systems if you do
a lot of compiling:

	% alias cc "cc -I/usr/local/include -L/usr/local/lib/X11"
	% alias ld "ld  -L/usr/local/lib/X11"

Note that some Berkeley systems (like Alliant Concentrix) don't support
the -L switch, but do allow you to specify directories to search for
libraries in different ways (Alliant Concentrix uses the environment
variable LD_PATH).

  Things would be even easier if R4 installed "imake" when one did ``make
install'' and made imake capable of differentiating a ``stand alone
compile'' from a ``production compile'' (i.e. compiling from within the
X11 source tree for boot strapping or development purposes as opposed to
using installed include and library files) ... (hint hint) We'd certainly
see more people using imake ...

  I would say that one of the nicest ways of doing this would be to give
imake a default include path to search for a default Makefile template
(ex:  $(INCDIR)/imake and "Imake.tmpl") and use something like ``imake
-DSTAND_ALONE ...'' which Imake.tmpl would use to properly construct a
Makefile for stand alone purposes.  ``make World'' would then use ``imake
-DSTAND_ALONE -T $(TOP)/util/imake.includes/Imake.tmpl''.  If people
doing Imake.tmpl development wanted to test out new template files they
could just have an Imake.tmpl, site.def, etc. files in the current
directory which would match the include specification before those in
$(INCDIR)/imake ...

  Makedepend also needs to be installed obviously, but I think we should
be thinking about using available tools here.  Berkeley now uses the shell
script "mkdep" to do this job and distributed it with 4.3-tahoe.  It
would be nice if we could get together on this.

  Just something I'd like to see in R4 ... :-) (P.S. I'll do the work for
this if no one in the X development group has the time.)

Casey