You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When building the project statically and then installing to CMAKE_INSTALL_PREFIX, on Unix the anchoring logic that determines where to search for libanari_device_XXX.so will base the search path off the folder that the executables are located in (i.e., bin) and thus won't find the actual device library (which is installed to lib). Therefore, static builds currently only work when being used from the build tree.
The text was updated successfully, but these errors were encountered:
Closing this as it is expected behavior -- the library anchoring search path checks the binary which the anchor is defined, where if it is static it will necessarily be the executable that linked libanari.a. Using LD_LIBRARY_PATH will still function, though, as well any RPATH injected by the linking executable.
When building the project statically and then installing to
CMAKE_INSTALL_PREFIX
, on Unix the anchoring logic that determines where to search forlibanari_device_XXX.so
will base the search path off the folder that the executables are located in (i.e.,bin
) and thus won't find the actual device library (which is installed tolib
). Therefore, static builds currently only work when being used from the build tree.The text was updated successfully, but these errors were encountered: