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.
NOTE: If this package has multiple flavors (see below), then use one of them instead of the name specified above. NOTE: This is a Python port. Instead of py312-pyopencl listed in the above command, you can pick from the names under the Packages section.
all: remove explicit versions in USES=python for "3.x+"
The logic in USES=python will automatically convert this to 3.8+ by
itself.
Adjust two ports that only had Python 3.7 mentioned but build fine
on Python 3.8 too.
finance/quickfix: mark BROKEN with PYTHON
libtool: compile: c++ -DHAVE_CONFIG_H -I. -I../.. -I -I. -I.. -I../.. -I../C++
-DLIBICONV_PLUG -DPYTHON_MAJOR_VERSION=3 -Wno-unused-variable
-Wno-maybe-uninitialized -O2 -pipe -DLIBICONV_PLUG -fstack-protector-strong
-fno-strict-aliasing -DLIBICONV_PLUG -Wall -ansi
-Wno-unused-command-line-argument -Wpointer-arith -Wwrite-strings
-Wno-overloaded-virtual -Wno-deprecated-declarations -Wno-deprecated -std=c++0x
-MT _quickfix_la-QuickfixPython.lo -MD -MP -MF
.deps/_quickfix_la-QuickfixPython.Tpo -c QuickfixPython.cpp -fPIC -DPIC -o
.libs/_quickfix_la-QuickfixPython.o
warning: unknown warning option '-Wno-maybe-uninitialized'; did you mean
'-Wno-uninitialized'? [-Wunknown-warning-option]
QuickfixPython.cpp:175:11: fatal error: 'Python.h' file not found
^~~~~~~~~~
1 warning and 1 error generated.
Reviewed by: portmgr, vishwin, yuri
Differential Revision: <https://reviews.freebsd.org/D40568>
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Bump PORTREVISION for ports depending on the canonical version of GCC
as defined in Mk/bsd.default-versions.mk which has moved from GCC 8.3
to GCC 9.1 under most circumstances now after revision 507371.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, everything INDEX-11 shows with a dependency on lang/gcc9 now.
PR: 238330
devel/py-pyopencl: fix build
Add USES=compiler:c++11-lang to fix:
RuntimeError: Unsupported compiler -- at least C++11 support is needed!
Approved by: mentors (implicit approval)
Bump PORTREVISION for ports depending on the canonical version of GCC
defined via Mk/bsd.default-versions.mk which has moved from GCC 7.4 t
GCC 8.2 under most circumstances.
This includes ports
- with USE_GCC=yes or USE_GCC=any,
- with USES=fortran,
- using Mk/bsd.octave.mk which in turn features USES=fortran, and
- with USES=compiler specifying openmp, nestedfct, c11, c++0x, c++11-lang,
c++11-lib, c++14-lang, c++17-lang, or gcc-c++11-lib
plus, as a double check, everything INDEX-11 showed depending on lang/gcc7.
PR: 231590
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
Corrected shared library names that got the .abi3 suffix for python-36 and up
after devel/py-cffi upgrade to 1.11.2
This is the followup for the r457997 commit that updated devel/py-cffi to
1.11.2.
As it turned out, the shared object names built by py-cffi has changed in python
36.
Dependent ports can choose between installing such shared object as part of
their plist, or
generating them in the runtime and placing them into ~/.cache/{port-name}/ The
former ones,
that include the shared objects in their plist, got affected.
4 of the ports were failing explicitly in their py36 flavor during the strip
phase.
The other 6 were either missing strip entirely, or performed the strip operation
without
using explicit shared object names. These 6 ports didn't trigger any build
errors, and were
failing silently during the runtime, making the problem very hard to detect.
Precisely, .abi3 suffix is now added for the py36 flavor of relevant ports.
Here are the 10 ports that got affected and are now corrected:
databases/py-psycopg2cffi devel/py-pygit2 devel/py-xattr devel/py-pyopencl
devel/py-atomiclong
multimedia/py-librtmp net/py-nnpy security/py-bcrypt security/py-cryptography
security/py-pynacl
All of them got the * in the stripped shared object name, and a PORTREVISION
bump.
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
(Only the first 15 lines of the commit message are shown above )
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
