pkgsrc/chat/fugu/Makefile

# $NetBSD: Makefile,v 1.7 2003/03/14 19:37:32 jlam Exp $
#

DISTNAME=	fugu-1.0
CATEGORIES=	chat
MASTER_SITES=	http://fugu.gale.org/dist/

MAINTAINER=	lukem@netbsd.org
HOMEPAGE=	http://fugu.gale.org
COMMENT=	graphical client for the gale secure instant messaging system

PYTHON_VERSIONS_ACCEPTED= 20 21 # no 22 - uses Makefile.pre.in

USE_BUILDLINK2=	YES
GNU_CONFIGURE= 	YES
CONFIGURE_ENV+=	vi_cv_path_python=${PYTHONBIN}
LDFLAGS+=	-L${BUILDLINK_PREFIX.py-Pmw}/lib \
		-Wl,${RPATH_FLAG}${BUILDLINK_PREFIX.py-Pmw}/lib
CPPFLAGS+=	-I${BUILDLINK_PREFIX.py-Pmw}/include \
		-I${BUILDLINK_PREFIX.rsaref}/include/rsaref \
		-I${BUILDLINK_PREFIX.rsaref}/include

.include "../../lang/python/application.mk"
.include "../../security/rsaref/buildlink2.mk"
.include "../../x11/py-Pmw/buildlink2.mk"
.include "../../mk/bsd.pkg.mk"
(1) Publicly export the value of _OPSYS_RPATH_NAME as RPATH_FLAG; Makefiles simply need to use this value often, for better or for worse. (2) Create a new variable FIX_RPATH that lists variables that should be cleansed of -R or -rpath values if ${_USE_RPATH} is "no". By default, FIX_RPATH contains LIBS, X11_LDFLAGS, and LDFLAGS, and additional variables may be appended from package Makefiles. 2003-03-14 20:37:30 +01:00			`# $NetBSD: Makefile,v 1.7 2003/03/14 19:37:32 jlam Exp $`
fugu - graphical gale client 2001-02-16 21:51:14 +01:00			`#`

			`DISTNAME= fugu-1.0`
			`CATEGORIES= chat`
			`MASTER_SITES= http://fugu.gale.org/dist/`

			`MAINTAINER= lukem@netbsd.org`
			`HOMEPAGE= http://fugu.gale.org`
			`COMMENT= graphical client for the gale secure instant messaging system`

convert to new Python framework 2002-01-29 12:33:54 +01:00			`PYTHON_VERSIONS_ACCEPTED= 20 21 # no 22 - uses Makefile.pre.in`
fugu - graphical gale client 2001-02-16 21:51:14 +01:00
+USE_BUILDLINK2 (hi wiz!). 2002-12-08 03:17:45 +01:00			`USE_BUILDLINK2= YES`
fugu - graphical gale client 2001-02-16 21:51:14 +01:00			`GNU_CONFIGURE= YES`
convert to new Python framework 2002-01-29 12:33:54 +01:00			`CONFIGURE_ENV+= vi_cv_path_python=${PYTHONBIN}`
buildlink1 -> buildlink2. 2002-10-12 13:21:25 +02:00			`LDFLAGS+= -L${BUILDLINK_PREFIX.py-Pmw}/lib \`
(1) Publicly export the value of _OPSYS_RPATH_NAME as RPATH_FLAG; Makefiles simply need to use this value often, for better or for worse. (2) Create a new variable FIX_RPATH that lists variables that should be cleansed of -R or -rpath values if ${_USE_RPATH} is "no". By default, FIX_RPATH contains LIBS, X11_LDFLAGS, and LDFLAGS, and additional variables may be appended from package Makefiles. 2003-03-14 20:37:30 +01:00			`-Wl,${RPATH_FLAG}${BUILDLINK_PREFIX.py-Pmw}/lib`
buildlink1 -> buildlink2. 2002-10-12 13:21:25 +02:00			`CPPFLAGS+= -I${BUILDLINK_PREFIX.py-Pmw}/include \`
			`-I${BUILDLINK_PREFIX.rsaref}/include/rsaref \`
			`-I${BUILDLINK_PREFIX.rsaref}/include`
fugu - graphical gale client 2001-02-16 21:51:14 +01:00
Strip the ".buildlink" from the names of the python application and extension Makefile fragments, because they really don't have anything to do with the buildlink[12] frameworks. Change all the Makefiles that use application.buildlink.mk and extension.buildlink.mk to use application.mk and extension.mk instead. 2002-09-22 01:46:45 +02:00			`.include "../../lang/python/application.mk"`
buildlink1 -> buildlink2. 2002-10-12 13:21:25 +02:00			`.include "../../security/rsaref/buildlink2.mk"`
			`.include "../../x11/py-Pmw/buildlink2.mk"`
fugu - graphical gale client 2001-02-16 21:51:14 +01:00			`.include "../../mk/bsd.pkg.mk"`