o use internal freetype2 for consistency with x11/XFree86-4.
o added xthreads obtained from x11/XFree86-4.
o install "ws" type config sample for xdm.
o build DRI only if kernel source installed in /sys.
o fix Riva128/SGRAM driver(patch-riva_hw.c).
PR: 24338(4.0.2)
Submitted by: maintainer, keith
bsd.port.mk, for easy removal of documentation. I left alone one port -
japanese/elisa8x8 (or something like that), because it appeared to have
some rather weird way of doing PORTDOCS substitution.
months. This should fix the build on 5-CURRENT and help some video
chips. See x11/XFree86's history for details.
Approved by: Taguchi Takeshi <taguchi@tohoku.iij.ad.jp> (MAINTAINER)
Submitted by: maintainer
(1) Respect CFLAGS when compiling shared libraries and servers.
(imake-4, XFree86-4-libraries)
Reported by: asami
(2) Do not redefine list of supported cards, and support architectures
other than i386 better.
(imake-4, XFree86-4-Server)
Obtained from: David Chaiken <chaiken@pa.dec.com>
x2x allows the keyboard and mouse on one ("from") X display to be used
to control another ("to") X display. Since x2x uses the XTEST
extension, the "to" X display must support XTEST.
In the default interface, x2x puts a window on the "from" display.
This window is labeled with the name of the "to" display. Keystrokes
typed into this window go to the window on the "to" display that has
the input focus. Clicking on the x2x window causes the mouse on the
"from" display to control the cursor on the "to" display. Perform-
ing a subsequent multiple button click on the "to" display returns
control to the "from" display.
If the -east or -west options are specified on the command line, x2x
starts up with a different interface. When the mouse moves to the
(east or west) side of the default screen on the "from" display, the
cursor slides over to the "to" display. When the mouse returns to to
side of the "to" display that it entered, it slides back onto the
"from" display.
XFree86 (3 or 4) to depend to when USE_XLIB is set.
XFREE86_VERSION defaults to 3 for now, but adventurous users can
override it in /etc/make.conf. When XFREE86_VERSION=3, USE_XLIB
will add a dependency to x11/XFree86; when it is set to 4, the
dependency will be to x11/XFree86-4-libraries. When
XFREE86_VERSION=4, the PKG_IGNORE_DEPENDS and ALWAYS_BUILD_DEPENDS
hacks to avoid messing with XFree86 are turned off.
Since XFree86 version 4 includes some software that used to be
separate ports, when XFREE86_VERSION=3 the following variables are
provided:
USE_DGS LIB_DEPENDS on x11/dgs
USE_FREETYPE LIB_DEPENDS on print/freetype
USE_MESA LIB_DEPENDS on graphics/Mesa3
USE_XPM LIB_DEPENDS on graphics/xpm
When XFREE86_VERSION=4, these variables have no effect. The
LIB_DEPENDS in the tree for the above four ports have all been
converted to the USE_* counterparts. For your information, this
is the count of the number of ports:
USE_DGS 0
USE_FREETYPE 16
USE_MESA 36
USE_XPM 236
There is a new variable, XAWVER, which is set to 6 when
XFREE86_VERSION=3 and 7 when XFREE86_VERSION=4. This is also
passed to PLIST_SUB so ports that build Xaw based shared libraries
can use this variable to substitute the shlib version number.
There is also a provision of using a separate mtree file for
XFREE86_VERSION=4, but that part is not enabled yet.
Reviewed by: the ports list
Tested by: make index (XFREE86_VERSION=3 only)
(2) Add hebrew to list of valid categories.
Submitted by: nbm
xfstt core dumps at times, especially when trying to serve the
regular "Courier New" font (COUR.TTF). As a result, X clients
trying to set the font will hang, and killing the hung clients
brings down X.
The problem is that xfstt calls realloc(), through its #define
shrinkMem(), but neglects to adjust a pointer that used to
point to memory within the old block. A subsequent copying of
that pointer then merrily SIGSEGV's the code.
PR: 19716
Submitted by: Chan Tur Wei <twchan@singnet.com.sg>
previous commit message to bsd.port.mk, which said INSTALL_SHLIBS. Boo.)
Line up the rhs of variable assignments nicely. Remove a couple of extra
whitespaces while I'm here.
Suggested by: sobomax
etc.) but I added five .o files to Server.
When we move to these ports as default, BSD.x11.dist will be changed so
we can get rid of all the @dirrm's.
Submitted by: bento