ee68c93314
set OVERRIDE_DIRDEPTH to find any libtool scripts deeper in the WRKSRC tree unless they're named something other than "libtool". SHLIBTOOL_OVERRIDE generally doesn't need to be specified either -- just define it to the empty list and shlibtool-override will look for libtool scripts.
41 lines
1.2 KiB
Makefile
41 lines
1.2 KiB
Makefile
# $NetBSD: Makefile,v 1.23 2006/07/07 15:49:32 jlam Exp $
|
|
|
|
PKGNAME= ${PYPKGPREFIX}-subversion-${SVNVER}
|
|
COMMENT= Python bindings and tools for Subversion
|
|
|
|
.include "../../devel/subversion/Makefile.common"
|
|
|
|
SHLIBTOOL_OVERRIDE= # empty
|
|
|
|
CONFIGURE_ENV+= PYTHON2=${PYTHONBIN:Q}
|
|
|
|
PY_PATCHPLIST= YES
|
|
PYBINMODULE= YES
|
|
PYTHON_PATCH_SCRIPTS= tools/hook-scripts/mailer/mailer.py
|
|
|
|
BUILD_TARGET= swig-py-lib swig-py
|
|
INSTALL_TARGET= install-swig-py
|
|
|
|
MAKE_ENV+= EXTRA_CPPFLAGS=${BUILDLINK_CPPFLAGS:Q}
|
|
MAKE_FLAGS+= swig_pydir=${LOCALBASE}/${PYSITELIB}/libsvn \
|
|
swig_pydir_extra=${LOCALBASE}/${PYSITELIB}/svn
|
|
|
|
TEST_TARGET= all check check-swig-py
|
|
|
|
post-patch:
|
|
${RM} ${WRKSRC}/build-outputs.mk
|
|
${CP} ${FILESDIR}/build-outputs.mk ${WRKSRC}/build-outputs.mk
|
|
|
|
post-install:
|
|
${INSTALL_DATA_DIR} ${SVNEXAMPLES}/python
|
|
${INSTALL_DATA} ${WRKSRC}/tools/examples/*.py ${SVNEXAMPLES}/python
|
|
${INSTALL_DATA} ${WRKSRC}/tools/hook-scripts/mailer/mailer.py \
|
|
${SVNEXAMPLES}/hook-scripts
|
|
${INSTALL_DATA} \
|
|
${WRKSRC}/tools/hook-scripts/mailer/mailer.conf.example \
|
|
${SVNEXAMPLES}/hook-scripts
|
|
|
|
.include "../../devel/subversion-base/buildlink3.mk"
|
|
.include "../../lang/python/application.mk"
|
|
.include "../../lang/python/extension.mk"
|
|
.include "../../mk/bsd.pkg.mk"
|