Files
Charlie Li 4f0eba1efd python.mk: rename PYTHON_EXT_SUFFIX to PYTHON_TAG, document, etc
EXT_SUFFIX, according to PEP 3149, refers to the full tag and
extension for compiled extension module objects, eg .cpython-311.so,
.cpython-313t.so, etc. We do not use the correct semantic meaning,
and this usage becomes ambiguous and confusing when tags do not
match between bytecode and compiled extension module objects.

Rename our PYTHON_EXT_SUFFIX to PYTHON_TAG to align with PEP 3147's
specification of a magic tag, which consists of implementation name
and shorthand version only. This is meant for bytecode and other
files containing this tag in their filename that do not depend on
a specific Python ABI for the same version. Chase all existing
consumers.

Introduce PYTHON_SOABI to align with PEP 3149's specification of a
tag, which consists of implementation name, shorthand version and
any ABI flags present (this and PYTHON_TAG are identical without
ABI flags). This is meant for compiled extension module objects and
other files that depend on a specific Python ABI for the same
version.

Add documentation for these variables that our PYTHON_EXT_SUFFIX
never had.

PR: 274671
Event: Kitchener-Waterloo Hackathon 202506
2025-06-19 16:28:47 -04:00

48 lines
1.3 KiB
Makefile

PORTNAME= openvdb
DISTVERSIONPREFIX= v
DISTVERSION= 12.0.1
PORTREVISION= 1
CATEGORIES= misc
PKGNAMEPREFIX= ${PYTHON_PKGNAMEPREFIX}
MAINTAINER= yuri@FreeBSD.org
COMMENT= Tools for storage and manipulation of sparse volumetric data
WWW= https://www.openvdb.org \
https://github.com/AcademySoftwareFoundation/openvdb
LICENSE= MPL20
LICENSE_FILE= ${WRKSRC}/../../../LICENSE
BUILD_DEPENDS= nanobind>0:devel/nanobind \
${PYNUMPY}
LIB_DEPENDS= libboost_iostreams.so:devel/boost-libs \
libopenvdb.so:misc/openvdb \
libtbb.so:devel/onetbb
RUN_DEPENDS= ${PYNUMPY}
USES= cmake compiler:c++17-lang localbase:ldflags python
USE_LDCONFIG= yes
USE_PYTHON= flavors pytest
USE_GITHUB= yes
GH_ACCOUNT= AcademySoftwareFoundation
CMAKE_ON= USE_NUMPY OPENVDB_PYTHON_WRAP_ALL_GRID_TYPES
CMAKE_OFF= OPENVDB_BUILD_PYTHON_UNITTESTS
CMAKE_ARGS= -DPython_EXECUTABLE=${PYTHON_CMD} \
-DFREEBSD_PYTHON_VER=${PYTHON_VER}
WRKSRC_SUBDIR= openvdb/openvdb/python
TEST_ENV= ${MAKE_ENV} PYTHONPATH=${STAGEDIR}${PYTHONPREFIX_SITELIBDIR}
PLIST_FILES= ${PYTHON_SITELIBDIR}/openvdb${PYTHON_TAG}.so
do-test: # run an example, since the supplied test appears to be only for Windows
@cd ${WRKSRC} && \
${SETENV} ${TEST_ENV} ${PYTHON_CMD} ${FILESDIR}/example.py && \
[ -f ${WRKSRC}/mygrids.vdb ] && \
${ECHO} "Test has succeeded."
.include <bsd.port.mk>