Okay, I didn’t take into account that change you mentioned previously for noetic… I tried adding the python3 part, and it showed the
Failed to stage: Parts 'sick-app-workspace' and 'python-part' have the following files, but with different contents:
lib64
So I followed the solution mentioned here
stage:
- lib64/*
But the prime fails because the python-part part has a lot of missing libraries
The 'python-part' part is missing libraries that are not included in the snap or base. They can be satisfied by adding the following entry for this part stage-packages: - libgl1 - libglvnd0 - libglx0 - libgomp1 - libusb-1.0-0 - libx11-6 - libxau6 - libxcb1 - libxdmcp6 This part is missing libraries that cannot be satisfied with any available stage-packages known to snapcraft: - libc10.so - libc10_cuda.so - libcublas.so.10 - libcudart.so.10.1 - libcusolver.so.10 - libnvToolsExt.so.1 - libtensorflow_framework.so.2 - libtorch.so - libtorch_cpu.so - libtorch_cuda.so These dependencies can be satisfied via additional parts or content sharing. Consider validating configured filesets if this dependency was built. The execstacks are going to be cleared for the following files: - /root/prime/lib/python3.8/site-packages/open3d/cuda/pybind.cpython-38-x86_64-linux-gnu.so - /root/prime/lib/python3.8/site-packages/open3d/cpu/pybind.cpython-38-x86_64-linux-gnu.so To disable this behavior set `build-attributes: [keep-execstack]` for the part.
Before I import those libraries into stage-packages , I would like to know if it is a good way to solve the open3d issue…