pkgsrc - [no description]

Age	Commit message (Collapse)	Author	Files	Lines
2003-06-12	Initiate support for X11 apps under IRIX.	jschauma	1	-4/+8
	We introduce two new variables: ABI and IMAKEOPTS ABI determines the correct ABI to use and is set during bootstrapping from /etc/compiler.defaults. IMAKEOPTS are the options passed to imake to allow it to set the right definitions and find the right paths etc. Use IMAKEOPTS with SunOS, too. IRIX will always require xpkgwedge, since it's got a bogus X11BASE. When linking against libXaw, make sure we get the right ABI.
2002-10-22	Have USE_IMAKE imply USE_X11BASE imply USE_X11. Now we can just check if	jlam	1	-2/+2
	USE_X11 is defined instead of USE_X11 \|\| USE_X11BASE \|\| USE_IMAKE.
2002-10-08	Note this this file is not for use by package Makefiles.	jlam	1	-1/+4

2002-09-27	Create a new variable USE_X11_LINKS that controls whether packages that	jlam	1	-0/+17
	use buildlink2 and set USE_X11 will use x11-links, or if they will simply symlink the X11 files directly into ${BUILDLINK_DIR}. If USE_X11_LINKS is "YES" (the default), then x11-links is used. If USE_X11_LINKS is "NO", then the X11 files are symlinked directly. There is a choice here between speed and flexibility. Using x11-links is faster since you don't need to spend time symlinking all of the X11 files into ${BUILDLINK_DIR}. However, if you update your X11 installation, then the x11-links package will likely be out-of-date. Conversely, directly symlinking the X11 files will protect you from changes in your X11 installation when you update, but there is a (small) time penalty to have to do it for every package that uses X11.