Path: utzoo!censor!geac!jtsv16!uunet!snorkelwacker!bloom-beacon!ATHENA.MIT.EDU!swick
From: swick@ATHENA.MIT.EDU (Ralph R. Swick)
Newsgroups: comp.windows.x
Subject: Re: X11R4 include change question
Message-ID: <8911131718.AA24392@LYRE.MIT.EDU>
Date: 13 Nov 89 17:18:28 GMT
References: <1989Nov13.142708.11897@sony.com>
Sender: daemon@bloom-beacon.MIT.EDU
Organization: DEC/MIT Project Athena
Lines: 20

> I suppose pre-R4 users
> can create a symbolic link in /usr/include/X11 to itself called Xaw,

For applications written to the R3 include directory structure,
R4/Xaw will have a configuration option to install the Xaw headers
in such a way that those applications will build.

For applications written to R4, there's no guarantee that they will
work with R3 (bugs fixed, etc.) -- even if the names are back-translated,
so it's not clear that simply aliasing the header files is an
appropriate thing to do.  Intrinsic.h has a (new) symbol which
you could use to tell if Xt is updated or not, so you might take
this as a hint to know where to look for Xaw headers, but I'd
advise any application wanting to build under R3 to explicitly
test its own configuration symbol (e.g. '#ifdef R3') in every
place that matters.

If the application really believes that the old header files will
work as-is, then in its own build directory it can create a link
from Xaw to /usr/include/X11 and add -I. to the compile command.