tech-pkg archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: python as a tool ?
> Date: Fri, 25 Sep 2026 21:31:33 +0200
> From: Manuel Bouyer <bouyer%antioche.eu.org@localhost>
>
> I'm working on a package which stops with:
> -- Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter)
> -- Packing libraries before installation
> CMake Error at CMakeLists.txt:60 (message):
> Python3 not found. Cannot pack symbol libraries.
> Call Stack (most recent call first):
> CMakeLists.txt:128 (pack_all_libraries)
>
> It actually wants to run a python script in the build phase.
> AFAIK it doens't need it as a runtime dependancy.
>
> We can do e.g.
> USE_TOOLS+= perl:build
>
> but it seems USE_TOOLS doens't supports python.
>
> What would be the best way to handle this ?
PYTHON_FOR_BUILD_ONLY= tool
.include "../../lang/python/pyversion.mk"
And, if you need it:
CMAKE_CONFIGURE_ARGS+= -DPython3_EXECUTABLE:STRING=${TOOL_PYTHONBIN:Q}
> In this specific case, a runtime dependancy on python isn't that bad as
> this package (kicad-symbols) is useless without kicad, which has a runtime
> dependancy on python.
Even if it's also a runtime dependency, for cross-builds, the path is
often different and must not be confused between the two purposes.
Home |
Main Index |
Thread Index |
Old Index