kpriv/freebsd-ports
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
freebsd-ports/devel/py-pyopencl/Makefile

46 lines
1.5 KiB
Makefile
Raw Normal View History

PyOpenCL gives you easy, Pythonic access to the OpenCL parallel computation API. What makes PyOpenCL special? - Object cleanup tied to lifetime of objects. This idiom, often called RAII in C++, makes it much easier to write correct, leak- and crash-free code. - Completeness. PyOpenCL puts the full power of OpenCL's API at your disposal, if you wish. Every obscure get_info() query and all CL calls are accessible. - Automatic Error Checking. All errors are automatically translated into Python exceptions. - Speed. PyOpenCL's base layer is written in C++, so all the niceties above are virtually free. - Helpful Documentation. - Liberal license. PyOpenCL is open-source under the MIT license and free for commercial, academic, and private use. WWW: http://mathema.tician.de/software/pyopencl
2015-10-15 02:15:24 +02:00
# $FreeBSD$
PORTNAME= pyopencl
Update to 2018.1.1 Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/inducer/pyopencl/commits/master
2018-02-25 18:10:50 +01:00
PORTVERSION= 2018.1.1
Bump PORTREVISIONs of all users of math/mpc that we just updated to version 1.1.0 (via revision 464079).
2018-03-10 18:46:04 +01:00
PORTREVISION= 1
PyOpenCL gives you easy, Pythonic access to the OpenCL parallel computation API. What makes PyOpenCL special? - Object cleanup tied to lifetime of objects. This idiom, often called RAII in C++, makes it much easier to write correct, leak- and crash-free code. - Completeness. PyOpenCL puts the full power of OpenCL's API at your disposal, if you wish. Every obscure get_info() query and all CL calls are accessible. - Automatic Error Checking. All errors are automatically translated into Python exceptions. - Speed. PyOpenCL's base layer is written in C++, so all the niceties above are virtually free. - Helpful Documentation. - Liberal license. PyOpenCL is open-source under the MIT license and free for commercial, academic, and private use. WWW: http://mathema.tician.de/software/pyopencl
2015-10-15 02:15:24 +02:00
CATEGORIES= devel python
MASTER_SITES= CHEESESHOP
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= python@FreeBSD.org
COMMENT= Python wrapper for OpenCL
LICENSE= MIT
Update to 2017.1.1 - Add LICENSE_FILE Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/pyopencl/pyopencl/commits/master
2017-06-06 15:51:30 +02:00
LICENSE_FILE= ${WRKSRC}/LICENSE
PyOpenCL gives you easy, Pythonic access to the OpenCL parallel computation API. What makes PyOpenCL special? - Object cleanup tied to lifetime of objects. This idiom, often called RAII in C++, makes it much easier to write correct, leak- and crash-free code. - Completeness. PyOpenCL puts the full power of OpenCL's API at your disposal, if you wish. Every obscure get_info() query and all CL calls are accessible. - Automatic Error Checking. All errors are automatically translated into Python exceptions. - Speed. PyOpenCL's base layer is written in C++, so all the niceties above are virtually free. - Helpful Documentation. - Liberal license. PyOpenCL is open-source under the MIT license and free for commercial, academic, and private use. WWW: http://mathema.tician.de/software/pyopencl
2015-10-15 02:15:24 +02:00
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g. With hat: portmgr Sponsored by: Absolight
2016-04-01 16:00:51 +02:00
BUILD_DEPENDS= ${LOCALBASE}/include/CL/cl.h:devel/opencl \
Convert Python ports to FLAVORS. Ports using USE_PYTHON=distutils are now flavored. They will automatically get flavors (py27, py34, py35, py36) depending on what versions they support. There is also a USE_PYTHON=flavors for ports that do not use distutils but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if using distutils but flavors are not wanted. A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added to cope with Python ports that did not have the Python PKGNAMEPREFIX but are flavored. USES=python now also exports a PY_FLAVOR variable that contains the current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464
2017-11-30 16:50:30 +01:00
${PYTHON_PKGNAMEPREFIX}cffi>=1.1.0:devel/py-cffi@${FLAVOR} \
${PYTHON_PKGNAMEPREFIX}numpy>=0:math/py-numpy@${FLAVOR}
devel/boost-python-libs got forgotten in the python flavorization, fix this oversight. Reviewed by: antoine Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D14368
2018-02-15 13:34:49 +01:00
LIB_DEPENDS= ${PY_BOOST} \
Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g. With hat: portmgr Sponsored by: Absolight
2016-04-01 16:00:51 +02:00
libOpenCL.so:devel/ocl-icd
Convert Python ports to FLAVORS. Ports using USE_PYTHON=distutils are now flavored. They will automatically get flavors (py27, py34, py35, py36) depending on what versions they support. There is also a USE_PYTHON=flavors for ports that do not use distutils but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if using distutils but flavors are not wanted. A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added to cope with Python ports that did not have the Python PKGNAMEPREFIX but are flavored. USES=python now also exports a PY_FLAVOR variable that contains the current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464
2017-11-30 16:50:30 +01:00
RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}appdirs>=1.4.0:devel/py-appdirs@${FLAVOR} \
${PYTHON_PKGNAMEPREFIX}cffi>=1.1.0:devel/py-cffi@${FLAVOR} \
${PYTHON_PKGNAMEPREFIX}decorator>=3.2.0:devel/py-decorator@${FLAVOR} \
${PYTHON_PKGNAMEPREFIX}mako>=0.3.6:textproc/py-mako@${FLAVOR} \
${PYTHON_PKGNAMEPREFIX}numpy>=0:math/py-numpy@${FLAVOR} \
${PYTHON_PKGNAMEPREFIX}pytest>=2:devel/py-pytest@${FLAVOR} \
Update to 2017.2.1 Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/inducer/pyopencl/commits/master
2017-12-16 21:56:11 +01:00
${PYTHON_PKGNAMEPREFIX}pytools>=2017.6:devel/py-pytools@${FLAVOR} \
Convert Python ports to FLAVORS. Ports using USE_PYTHON=distutils are now flavored. They will automatically get flavors (py27, py34, py35, py36) depending on what versions they support. There is also a USE_PYTHON=flavors for ports that do not use distutils but need FLAVORS to be set. A USE_PYTHON=noflavors can be set if using distutils but flavors are not wanted. A new USE_PYTHON=optsuffix that will add PYTHON_PKGNAMESUFFIX has been added to cope with Python ports that did not have the Python PKGNAMEPREFIX but are flavored. USES=python now also exports a PY_FLAVOR variable that contains the current python flavor. It can be used in dependency lines when the port itself is not python flavored. For example, deskutils/calibre. By default, all the flavors are generated. To only generate flavors for the versions in PYTHON2_DEFAULT and PYTHON3_DEFAULT, define BUILD_DEFAULT_PYTHON_FLAVORS in your make.conf. In all the ports with Python dependencies, the *_DEPENDS entries MUST end with the flavor so that the framework knows which to build/use. This is done by appending '@${PY_FLAVOR}' after the origin (or @${FLAVOR} if in a Python module with Python flavors, as the content will be the same). For example: RUN_DEPENDS= ${PYTHON_PKGNAMEPREFIX}six>0:devel/py-six@${PY_FLAVOR} PR: 223071 Reviewed by: portmgr, python Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D12464
2017-11-30 16:50:30 +01:00
${PYTHON_PKGNAMEPREFIX}six>=1.9.0:devel/py-six@${FLAVOR}
Update to 2017.1.1 - Add LICENSE_FILE Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/pyopencl/pyopencl/commits/master
2017-06-06 15:51:30 +02:00
CONFIGURE_ARGS= BOOST_INC_DIR="${LOCALBASE}/include" \
BOOST_LIB_DIR="${LOCALBASE}/lib" \
devel/boost-python-libs got forgotten in the python flavorization, fix this oversight. Reviewed by: antoine Sponsored by: Absolight Differential Revision: https://reviews.freebsd.org/D14368
2018-02-15 13:34:49 +01:00
BOOST_PYTHON_LIBNAME=${PY_BOOST_LIB} \
Update to 2017.1.1 - Add LICENSE_FILE Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/pyopencl/pyopencl/commits/master
2017-06-06 15:51:30 +02:00
CL_INC_DIR="${LOCALBASE}/include" \
CL_LIB_DIR="${LOCALBASE}/lib" \
USE_SHIPPED_BOOST=False
PyOpenCL gives you easy, Pythonic access to the OpenCL parallel computation API. What makes PyOpenCL special? - Object cleanup tied to lifetime of objects. This idiom, often called RAII in C++, makes it much easier to write correct, leak- and crash-free code. - Completeness. PyOpenCL puts the full power of OpenCL's API at your disposal, if you wish. Every obscure get_info() query and all CL calls are accessible. - Automatic Error Checking. All errors are automatically translated into Python exceptions. - Speed. PyOpenCL's base layer is written in C++, so all the niceties above are virtually free. - Helpful Documentation. - Liberal license. PyOpenCL is open-source under the MIT license and free for commercial, academic, and private use. WWW: http://mathema.tician.de/software/pyopencl
2015-10-15 02:15:24 +02:00
USE_PYTHON= autoplist distutils
Update to 2017.1.1 - Add LICENSE_FILE Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/pyopencl/pyopencl/commits/master
2017-06-06 15:51:30 +02:00
USES= localbase python
- Do not use bundled Boost.Python. - Do not unconditionally set "-O3" to CXXFLAGS.
2015-10-20 00:41:56 +02:00
do-configure:
@cd ${WRKSRC} && ${PYTHON_CMD} configure.py ${CONFIGURE_ARGS}
PyOpenCL gives you easy, Pythonic access to the OpenCL parallel computation API. What makes PyOpenCL special? - Object cleanup tied to lifetime of objects. This idiom, often called RAII in C++, makes it much easier to write correct, leak- and crash-free code. - Completeness. PyOpenCL puts the full power of OpenCL's API at your disposal, if you wish. Every obscure get_info() query and all CL calls are accessible. - Automatic Error Checking. All errors are automatically translated into Python exceptions. - Speed. PyOpenCL's base layer is written in C++, so all the niceties above are virtually free. - Helpful Documentation. - Liberal license. PyOpenCL is open-source under the MIT license and free for commercial, academic, and private use. WWW: http://mathema.tician.de/software/pyopencl
2015-10-15 02:15:24 +02:00
post-install:
Update to 2017.1.1 - Add LICENSE_FILE Changes: https://documen.tician.de/pyopencl/misc.html#user-visible-changes https://github.com/pyopencl/pyopencl/commits/master
2017-06-06 15:51:30 +02:00
${FIND} ${STAGEDIR}${PYTHON_SITELIBDIR}/ -name '*.so' -exec ${STRIP_CMD} {} +
PyOpenCL gives you easy, Pythonic access to the OpenCL parallel computation API. What makes PyOpenCL special? - Object cleanup tied to lifetime of objects. This idiom, often called RAII in C++, makes it much easier to write correct, leak- and crash-free code. - Completeness. PyOpenCL puts the full power of OpenCL's API at your disposal, if you wish. Every obscure get_info() query and all CL calls are accessible. - Automatic Error Checking. All errors are automatically translated into Python exceptions. - Speed. PyOpenCL's base layer is written in C++, so all the niceties above are virtually free. - Helpful Documentation. - Liberal license. PyOpenCL is open-source under the MIT license and free for commercial, academic, and private use. WWW: http://mathema.tician.de/software/pyopencl
2015-10-15 02:15:24 +02:00
.include <bsd.port.mk>
Reference in a new issue Copy permalink