sdk link issue with libnvinfer.so rpath and libcudla.so #1383
Unanswered
aurelien-enchanted-tools
asked this question in
Q&A
Replies: 1 comment 2 replies
-
The necessary compiler and linker flags/options to make the CUDA libraries available should get added automatically by CMake if you've told it you're using CUDA, either by specifying |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hello, I met an issue with the sdk and cmake during the link step
poky: langdale
meta-tegra: langdale
In the sdk, I have got:
/usr/local/oe-sdk-hardcoded-buildpath/sysroots/armv8a-custom-linux/usr/lib/libnvinfer.so
and/usr/local/oe-sdk-hardcoded-buildpath/sysroots/armv8a-custom-linux/usr/local/cuda-11.4/lib/libcudla.so.1
I check the c++ method cudlaSubmitTask is in
/usr/local/oe-sdk-hardcoded-buildpath/sysroots/armv8a-custom-linux/usr/local/cuda-11.4/lib/libcudla.so.1
In the image:
I would like to know:
/usr/local/oe-sdk-hardcoded-buildpath/sysroots/armv8a-custom-linux/usr/local/cuda-11.4/lib/
in the libnvinfer's RPATH, or betterThank you in advance.
Beta Was this translation helpful? Give feedback.
All reactions