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
Currently, Linux users that want to load shared objects from a non system path must use LD_LIBRARY_PATH which is not ideal if the application is being run on a system that doesn't have the environment variable set ahead of time.
This can be resolved by using -rpath -Wl,\$ORIGIN in LDFLAGS however, further consideration needs to be taken to decide if this should be added in the go build command similar to how we handle windows console hiding or if it should be included in the c-for-go generated bindings.
The text was updated successfully, but these errors were encountered:
Currently, Linux users that want to load shared objects from a non system path must use
LD_LIBRARY_PATH
which is not ideal if the application is being run on a system that doesn't have the environment variable set ahead of time.This can be resolved by using
-rpath -Wl,\$ORIGIN
inLDFLAGS
however, further consideration needs to be taken to decide if this should be added in thego build
command similar to how we handle windows console hiding or if it should be included in thec-for-go
generated bindings.The text was updated successfully, but these errors were encountered: