2012-01-08 10:36:26 -05:00
|
|
|
# $OpenBSD: Makefile,v 1.73 2012/01/08 15:36:26 dcoppa Exp $
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
2008-11-29 06:29:07 -05:00
|
|
|
COMMENT-main= screen saver and locker for the X Window System
|
|
|
|
COMMENT-data= graphical demos (savers) for screensavers
|
|
|
|
COMMENT-gle= OpenGL Extrusion library support for screensaver-data
|
|
|
|
|
2012-01-08 10:36:26 -05:00
|
|
|
V= 5.15
|
2008-11-29 06:29:07 -05:00
|
|
|
DISTNAME= xscreensaver-${V}
|
2010-04-15 05:16:07 -04:00
|
|
|
PKGNAME-main= ${DISTNAME}
|
2009-11-28 05:49:49 -05:00
|
|
|
PKGNAME-data= xscreensaver-data-${V}
|
|
|
|
PKGNAME-gle= xscreensaver-gle-${V}
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
2006-11-09 03:27:51 -05:00
|
|
|
CATEGORIES= x11
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
|
|
|
HOMEPAGE= http://www.jwz.org/xscreensaver/
|
|
|
|
|
2003-10-08 13:13:14 -04:00
|
|
|
# BSD
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
PERMIT_PACKAGE_CDROM= Yes
|
|
|
|
PERMIT_PACKAGE_FTP= Yes
|
|
|
|
PERMIT_DISTFILES_CDROM= Yes
|
|
|
|
PERMIT_DISTFILES_FTP= Yes
|
2005-06-03 01:38:32 -04:00
|
|
|
|
2011-10-12 02:55:56 -04:00
|
|
|
MULTI_PACKAGES= -main -data -gle
|
2008-11-29 06:29:07 -05:00
|
|
|
|
|
|
|
WANTLIB= GL GLU ICE SM X11 Xext Xmu Xpm Xt Xxf86vm c glib-2.0 \
|
2010-07-16 05:58:09 -04:00
|
|
|
gmodule-2.0 gobject-2.0 m pthread gthread-2.0
|
2008-11-29 06:29:07 -05:00
|
|
|
|
|
|
|
WANTLIB-main= ${WANTLIB} Xau Xcomposite Xcursor Xdamage Xdmcp Xfixes \
|
|
|
|
Xi Xinerama Xrandr Xrender Xxf86misc atk-1.0 cairo \
|
|
|
|
expat fontconfig freetype gdk-x11-2.0 gdk_pixbuf-2.0 \
|
2010-10-11 04:11:24 -04:00
|
|
|
gdk_pixbuf_xlib-2.0 gio-2.0 gtk-x11-2.0 jpeg \
|
2009-08-12 13:30:12 -04:00
|
|
|
pango-1.0 pangocairo-1.0 pangoft2-1.0 pixman-1 png \
|
2010-12-06 12:37:59 -05:00
|
|
|
pthread-stubs xcb xml2 z xcb-render glade-2.0 \
|
|
|
|
drm xcb-shm
|
2008-11-29 06:29:07 -05:00
|
|
|
|
2010-12-06 12:37:59 -05:00
|
|
|
WANTLIB-data= ${WANTLIB} jpeg util gdk_pixbuf-2.0 gdk_pixbuf_xlib-2.0 \
|
|
|
|
png z
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
2006-11-03 17:44:02 -05:00
|
|
|
MASTER_SITES= ${HOMEPAGE}
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
2008-03-17 14:59:39 -04:00
|
|
|
MODULES= devel/gettext \
|
|
|
|
textproc/intltool
|
2002-03-26 21:53:59 -05:00
|
|
|
|
2008-11-29 06:29:07 -05:00
|
|
|
# ${FILESDIR}/migrate-xscreensaver-config.sh needs xsltproc
|
2010-11-22 03:36:47 -05:00
|
|
|
BUILD_DEPENDS= textproc/libxslt
|
2008-11-29 06:29:07 -05:00
|
|
|
|
|
|
|
# note that we don't need desktop-file-utils for the -data subpackage
|
|
|
|
# because the desktop files it installs are under a subdirectory of
|
|
|
|
# ${LOCALBASE}/share/applications/
|
2010-11-22 03:36:47 -05:00
|
|
|
RUN_DEPENDS-main= devel/desktop-file-utils \
|
|
|
|
x11/xscreensaver,-data
|
2008-11-29 06:29:07 -05:00
|
|
|
|
|
|
|
LIB_DEPENDS-main= ${MODGETTEXT_LIB_DEPENDS} \
|
2010-11-22 03:36:47 -05:00
|
|
|
devel/libglade2
|
2008-11-29 06:29:07 -05:00
|
|
|
|
|
|
|
LIB_DEPENDS-data= ${MODGETTEXT_LIB_DEPENDS} \
|
2010-11-22 03:36:47 -05:00
|
|
|
graphics/gdk-pixbuf2
|
2002-03-26 21:53:59 -05:00
|
|
|
|
2002-06-25 22:36:03 -04:00
|
|
|
USE_GMAKE= Yes
|
2010-11-22 03:36:47 -05:00
|
|
|
USE_GROFF = Yes
|
2002-08-26 22:46:17 -04:00
|
|
|
NO_REGRESS= Yes
|
|
|
|
|
2005-06-03 01:38:32 -04:00
|
|
|
CONFIGURE_STYLE= gnu
|
2005-09-04 15:53:33 -04:00
|
|
|
CONFIGURE_ARGS+= --with-hackdir="${PREFIX}/libexec/xscreensaver" \
|
2006-11-03 17:44:02 -05:00
|
|
|
--with-x-app-defaults="${PREFIX}/lib/X11/app-defaults"
|
2007-07-18 07:26:30 -04:00
|
|
|
CONFIGURE_ENV+= CPPFLAGS="-I${LOCALBASE}/include" \
|
|
|
|
CFLAGS="${CFLAGS} -I${LOCALBASE}/include" \
|
2010-12-06 12:37:59 -05:00
|
|
|
LDFLAGS="-L${LOCALBASE}/lib -liconv -lintl"
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
2005-06-03 01:38:32 -04:00
|
|
|
# License issues with graphics/gle necessitate this
|
2008-11-29 06:29:07 -05:00
|
|
|
PSEUDO_FLAVORS= no_gle
|
2004-03-12 13:03:17 -05:00
|
|
|
FLAVOR?= no_gle
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
|
2011-10-12 02:55:56 -04:00
|
|
|
.include <bsd.port.arch.mk>
|
|
|
|
|
2008-11-29 06:29:07 -05:00
|
|
|
LIB_DEPENDS-gle= ${MODGETTEXT_LIB_DEPENDS} \
|
2010-11-22 03:36:47 -05:00
|
|
|
graphics/gle \
|
|
|
|
x11/gtk+2
|
2011-10-12 02:55:56 -04:00
|
|
|
RUN_DEPENDS-gle= ${BUILD_PKGPATH},-data
|
2010-07-16 05:58:09 -04:00
|
|
|
WANTLIB-gle= ${WANTLIB} gle gdk_pixbuf-2.0 gdk_pixbuf_xlib-2.0
|
2011-10-12 02:55:56 -04:00
|
|
|
|
|
|
|
.if ${BUILD_PACKAGES:M-gle}
|
2002-01-09 16:14:44 -05:00
|
|
|
CONFIGURE_ARGS+= --with-gle
|
|
|
|
.else
|
|
|
|
CONFIGURE_ARGS+= --without-gle
|
|
|
|
.endif
|
|
|
|
|
2008-10-27 15:49:39 -04:00
|
|
|
post-extract:
|
2008-11-29 06:29:07 -05:00
|
|
|
cp ${FILESDIR}/migrate-xscreensaver-config.sh ${WRKSRC}/hacks/config
|
|
|
|
cp ${FILESDIR}/xscreensaver-config.xsl ${WRKSRC}/hacks/config
|
2008-10-27 15:49:39 -04:00
|
|
|
|
2002-03-26 16:51:41 -05:00
|
|
|
post-install:
|
2008-11-29 06:29:07 -05:00
|
|
|
# remove conflict on games/circuit, misc/deco
|
|
|
|
for i in circuit deco ; do \
|
|
|
|
mv ${PREFIX}/man/man6/$${i}.6 ${PREFIX}/man/man6/x$${i}.6 ; \
|
|
|
|
mv ${PREFIX}/libexec/xscreensaver/$${i} \
|
|
|
|
${PREFIX}/libexec/xscreensaver/x$${i} && \
|
|
|
|
mv ${PREFIX}/share/xscreensaver/config/$${i}.xml \
|
|
|
|
${PREFIX}/share/xscreensaver/config/x$${i}.xml && \
|
|
|
|
mv ${WRKSRC}/hacks/config/$${i}.xml \
|
|
|
|
${WRKSRC}/hacks/config/x$${i}.xml ; done
|
|
|
|
cd ${WRKSRC}/hacks/config && \
|
|
|
|
for i in ${WRKSRC}/hacks/config/*.xml; do \
|
|
|
|
/bin/sh migrate-xscreensaver-config.sh $${i} ; done
|
|
|
|
# conflict with x11/gnome/screensaver and is not needed by xscreensaver per se
|
|
|
|
rm ${WRKSRC}/hacks/config/popsquares.desktop
|
|
|
|
${INSTALL_DATA_DIR} ${PREFIX}/share/applications/screensavers/
|
|
|
|
${INSTALL_DATA} ${WRKSRC}/hacks/config/*.desktop \
|
|
|
|
${PREFIX}/share/applications/screensavers/
|
2002-03-26 16:51:41 -05:00
|
|
|
|
The xscreensaver program waits until the keyboard and mouse have
been idle for a period, and then runs a graphics demo chosen at
random. It turns off as soon as there is any mouse or keyboard
activity. It can also lock the screen (immediately, after a longer
idle period, or on demand.) xscreensaver consists of two parts:
xscreensaver itself, the (the ``driver'' or ``daemon''), which
detects idleness and does locking; and the many graphics demos that
are launched by xscreensaver.
Any X program that can draw on the root window can be used with
xscreensaver, regardless of how that program is written, or what
language it is written in, or what libraries it uses. The xscreensaver
daemon takes care of detecting when the user is idle, locking, and
checking passwords and all the other book-keeping; all the other
programs need to do is draw.
The benefit that xscreensaver has over the combination of the xlock
and xautolock programs is the ease with which new graphics hacks
can be installed. You don't need to recompile (or even re-run) the
xscreensaver program to add a new display mode, you just change a
config file.
WWW: http://www.jwz.org/xscreensaver/
2001-06-20 15:16:45 -04:00
|
|
|
.include <bsd.port.mk>
|