AMD Radeon™ ProRender is a powerful physically-based path traced rendering engine that enables creative professionals to produce stunningly photorealistic images.
Maybe I'm the only person to try the samples under macOS, because it seems like they can't possibly work as written. In a nutshell, the built binaries try to load libRadeonProRender64.dylib at the path @rpath/libRadeonProRender64.dylib, however no LC_RPATH loader command is present, so at runtime the dylib is not found and the process exits.
andre@boop RadeonProRenderSDK % ./tutorials/Bin/03_instance64
dyld: Library not loaded: @rpath/libRadeonProRender64.dylib
Referenced from: /Users/andre/work/RadeonProRenderSDK/./tutorials/Bin/03_instance64
Reason: image not found
zsh: abort ./tutorials/Bin/03_instance64
andre@boop RadeonProRenderSDK % otool -l tutorials/Bin/03_instance64 | egrep -A 2 -i 'lc_load_dylib|lc_rpath'
cmd LC_LOAD_DYLIB
cmdsize 64
name @rpath/libRadeonProRender64.dylib (offset 24)
--
cmd LC_LOAD_DYLIB
cmdsize 48
name /usr/lib/libc++.1.dylib (offset 24)
--
cmd LC_LOAD_DYLIB
cmdsize 56
name /usr/lib/libSystem.B.dylib (offset 24)
Adding a load command to set LC_RPATH solves the problem. In my case:
Hello!
Maybe I'm the only person to try the samples under macOS, because it seems like they can't possibly work as written. In a nutshell, the built binaries try to load
libRadeonProRender64.dylib
at the path@rpath/libRadeonProRender64.dylib
, however noLC_RPATH
loader command is present, so at runtime the dylib is not found and the process exits.Adding a load command to set
LC_RPATH
solves the problem. In my case: