Linker issue GPU Coder generated static lib to g++ project.
3 views (last 30 days)
Show older comments
Hi
I generated a static libxyz.a with the GPU Coder on a Jetson Xavier target. Now I want to link this library into an existing g++ project.
Unfortunately I get unresolved symbols which directs to MathWorks methods like __cudaRegisterLinkedBinary_54_tmpxft_000031a2_00000000_6_MWTargetNetworkImpl_cpp1_ii_beb7
An internet search pointed me to a build example for such use case: https://docs.nvidia.com/cuda/cuda-compiler-driver-nvcc/index.html#examples
There's an intermediate linker step (--device-link) used before generating the static library, in this case libgpu.a:
nvcc --gpu-architecture=sm_50 --device-c a.cu b.cu
nvcc --gpu-architecture=sm_50 --device-link a.o b.o --output-file link.o
nvcc --lib --output-file libgpu.a a.o b.o link.o
g++ host.o --library=gpu --library-path=<path> \
--library=cudadevrt --library=cudart
Unfortunately I cannot find this --device-link step in the GPU Coders build log before the static library is linked from the object files.
Is there an coder option to enable such device-linker step? Or how could such unresolved symbold be resolved otherwise?
0 Comments
Answers (1)
Claudio Stucki
on 20 Nov 2019
Edited: Claudio Stucki
on 20 Nov 2019
Hi
I have the same problems. Have you found a solution to link your library successfully?
See Also
Categories
Find more on Get Started with GPU Coder in Help Center and File Exchange
Community Treasure Hunt
Find the treasures in MATLAB Central and discover how the community can help you!
Start Hunting!