summaryrefslogtreecommitdiff
path: root/mk/x11.buildlink2.mk
AgeCommit message (Collapse)AuthorFilesLines
2002-10-22Have USE_IMAKE imply USE_X11BASE imply USE_X11. Now we can just check ifjlam1-2/+2
USE_X11 is defined instead of USE_X11 || USE_X11BASE || USE_IMAKE.
2002-10-08Note this this file is not for use by package Makefiles.jlam1-1/+4
2002-09-27Create a new variable USE_X11_LINKS that controls whether packages thatjlam1-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.