On Tue, May 12, 2020 at 09:02:52PM +0200, Rafael Sadowski wrote:
> Yes and no. I saw the following lines in devel/llvm and thought I had
> caused it with my cmake changes. But this happens even without my
> changes, although we set MODPY_VERSION=${MODPY_DEFAULT_VERSION_3}.
Ah, good to know.> -- Could NOT find Python module pygments > -- Could NOT find Python module pygments.lexers.c_cpp > -- Found PythonInterp: /usr/local/bin/python2.7 (found version "2.7.18") > -- Found PythonLibs: /usr/local/lib/libpython2.7.so.0.0 (found version > "2.7.18") I thought we're missing some PYTHON_*=... during configure or so... > > This workaround should no longer exist for cmake ports. *WIP* > Preview: > https://github.com/sizeofvoid/wip-ports/commit/a1b2879b832e52f64788c89bed62d0ea17c0f8c8 then i saw you're doing just that in cmake.port.mk: + .if ${MODULES:Mlang/python} + # https://cmake.org/cmake/help/latest/module/FindPython3.html#artifacts-specification + CONFIGURE_ARGS += -DPYTHON_EXECUTABLE=${MODPY_BIN} + CONFIGURE_ARGS += -DPYTHON_LIBRARY_DIRS=${MODPY_LIBDIR} + CONFIGURE_ARGS += -DPYTHON_INCLUDE_DIR=${MODPY_INCDIR} + .endif That looks good, thanks.
