-
Hi guys, bitbake core-image-sato-dev Build Configuration: Initialising tasks: 100% |###################################################################################################################################################################| Time: 0:00:05 ... checking pkg-config is at least version 0.9.0... yes Its seems there is no recipe for python3.6 so its taking default python3.8 recipe but due to this error "configure: error: Python libs not found. Windows requires Python modules to be explicitly linked to libpython." build getting failed I just want to add deepstream python support in my image but struct in this problem. Please help me to proceed. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
Unfortunately, you cannot use the DeepStream Python bindings natively in a Yocto-built image due to their dependency on Python 3.6. If you really need Python+DeepStream, you could run them in a container. You could also contact RidgeRun, as mentioned on their wiki page, to ask about other alternatives. NVIDIA released source code for the Python bindings for DeepStream 6.0, so in theory, at least, we could have a recipe to build them, and that should make them compatible with whatever version of Python we have. No one has submitted a recipe for them yet. There does appear to be an issue with the gstreamer1.0-python 1.14 recipe we have in the contrib layer, which I'll take a look at. |
Beta Was this translation helpful? Give feedback.
Unfortunately, you cannot use the DeepStream Python bindings natively in a Yocto-built image due to their dependency on Python 3.6. If you really need Python+DeepStream, you could run them in a container. You could also contact RidgeRun, as mentioned on their wiki page, to ask about other alternatives.
NVIDIA released source code for the Python bindings for DeepStream 6.0, so in theory, at least, we could have a recipe to build them, and that should make them compatible with whatever version of Python we have. No one has submitted a recipe for them yet.
There does appear to be an issue with the gstreamer1.0-python 1.14 recipe we have in the contrib layer, which I'll take a look at.