eap@bu-cs.BU.EDU (Eric A. Pearce) (07/27/89)
In the process bringing up the toolkit and widget libraries, I noticed there does not seem to be a standard place to put them. For example: The core include files from X11, Xaw, Xt, Xmu, etc, all expect to be in /usr/include/X11. Xw wants to be in a separate directory (i.e /usr/include/Xw ) Xcu, Xsw get thrown in /usr/include. It seems you would want a separate sub-directory for each widget set when you have files of the same name with different libraries and just compile with "-I/usr/include/<widget or toolkit> -I/usr/include/X11" My first impulse would be to go look at how someone else set it up, but I don't know anybody who has everything in the core and contrib stuff running. Is there a "right" way to go about this? -e -- ------------------------------------------------------------------------------- Eric Pearce eap@bu-it.bu.edu Boston University Information Technology 111 Cummington Street Boston MA 02215 617-353-2780 voice 617-353-6260 fax
kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) (07/27/89)
> The core include files from X11, Xaw, Xt, Xmu, etc, all expect to be > in /usr/include/X11. In Release 4 both Xaw and Xmu will have their own subdirectory (Yes we will still support the old paths for this release for compatability with old releases). e.g /usr/include/X11/Xaw and /usr/include/X11/Xmu The idea is to keep those things that are Consortium Standards seperate from those that are just sample implementations. I believe that this is a pretty good place to put Widget include files, and would encourage other Widget implementors to follow the same example. Chris D. Peterson MIT X Consortium Net: kit@expo.lcs.mit.edu Phone: (617) 253 - 9608 Address: MIT - Room NE43-213
noams@sco.COM (Noam Stopak) (07/31/89)
In article <8907271547.AA17347@expo.lcs.mit.edu> kit@EXPO.LCS.MIT.EDU (Chris D. Peterson) writes: >In Release 4 both Xaw and Xmu will have their own subdirectory (Yes we will >still support the old paths for this release for compatability with old >releases). > >e.g /usr/include/X11/Xaw and /usr/include/X11/Xmu > >The idea is to keep those things that are Consortium Standards seperate >from those that are just sample implementations. >... Since verious vendors (I actually have OSF in mind, but I know HP has their own flavor too) have developed their own flavor of the intrinsics which define various structures which have different sizes than the MIT version (generally larger :-( ), might it not be a good idea to place Xt header files in a subdirectory as well? I have seen indications that Xt will become a standard, but this does not seem to be a reality at the moment :-( How about /usr/include/X11/Xt.MIT, /usr/include/X11/Xt.OSF etc? Noam Stopak noams@sco.com "There's nothing like a standard, and this is nothing like a standard"
rws@EXPO.LCS.MIT.EDU (07/31/89)
I have seen indications that Xt will become a standard, but this
does not seem to be a reality at the moment :-(
Xt is an X Consortium standard. Several vendors have done extensions to
the standard (generally upward compatible), and most of these (and a few
more) are under review within the Consortium for inclusion in the next
revision of the standard. Everyone involved is committed to converging
on a single Xt.
How about /usr/include/X11/Xt.MIT, /usr/include/X11/Xt.OSF etc?
Nope.