corresponding to the X11 files. This can be defined to be more complex
script than the default of "${LN} -fs $$src $$dest" if some of the files
need to have transformations performed on them.
something to check the shared library type.
(An entertaining way to pick up on issues seems to be to set CFLAGS to include
an argument not understood by the base compiler, such as '-march=pentium3')
Changes include supporting XFree86-4.3.99.14 aka XFree86-current.
Added some new library versions and some freetype2 include files.
And bump the required version number in the bsd.buildlink mk's.
on tech-pkg@ at various times. This means that regardless of what kind of
GL support comes with X11, if a package depends on GL, Mesa 5.0.1 (or higher)
will be installed into ${LOCALBASE}.
Some troubleshooting after the latest patches by Krister Walfridsson.
XSgi is based on Release 6 of the X Consortium distribution, but it also
has a whole bunch of symlinks into Motif libraries and headers.
When installing the links, grab the right ABI.
Changes:
- Support XFree86 4.2.99.3, so we support the upcoming 4.3
- There is no need to link bitmap files, which was introduced while
switching to bulidlink2
- Add the following new files:
include/X11/Xcursor/Xcursor.h
include/X11/extensions/bigreqstr.h
include/X11/extensions/extutil.h
include/X11/extensions/mitmiscstr.h
include/X11/extensions/multibufst.h
include/X11/extensions/shapestr.h
include/X11/extensions/shmstr.h
include/X11/extensions/syncstr.h
include/X11/extensions/xcmiscstr.h
include/X11/extensions/xteststr.h
lib/llibXcursor.a
lib/libXcursor.so
lib/libXcursor.so.1
lib/libXcursor.so.1.0
lib/libXrandr.so.2
lib/libXrandr.so.2.0
lib/libXrender.so.1.2
lib/libXv.so
lib/libXv.so.1
lib/libXv.so.1.0
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.
Use _REQUIRE_BUILTIN_* to specify that the headers/libraries of some parts
of X11 that are available from 3rd parties must be part of the standard X11
distribution or else their symlinks aren't installed as part of x11-links.
This is to allow x11-links to contain all of the parts of the standard X11
distribution.
The problem that prompted this is that newer releases of XFree86-4.x
contain not just new libraries but new inter-library dependencies. Some
of the X11 libraries present in XF86-4.x that were also in XF86-3.x now
depend on libXpm.so or libfreetype.so, which, from a buildlink
point-of-view, must also be found during the link phase when building
software.
libraries to ${X11BASE} under ${LOCALBASE}/share/x11-links. It is intended
for use by buildlink code to cleanly separate out the true X11 code files
from any installed X11 package code files. The X11 hierarchies supported
are:
XFree86-3.3.x
XFree86-4.0.x
XFree86-4.1.0
