Lack of documentation regarding shared libraries

[tropical32]

README.md lacks documentation regarding the integration of shared libraries. While executing a simple example using cargo run works seamlessly, building the project and executing the resulting binary leads to errors due to missing shared libraries. For instance:

$ target/release/steam_works                                                                  
target/release/steam_works: error while loading shared libraries: libsteam_api.so: cannot open shared object file: No such file or directory

Even manually copying the shared object to ./target/release does not resolve the issue. There's no clear indication or documentation provided on how to properly handle shared libraries or which global variables to update for it to work.

I found that moving libsteam_api.so to /lib supressed that error:
sudo cp libsteam_api.so /lib

In windows, steam_api64.dll should live in C:\Windows\system32

[honungsburk]

After some digging I discovered that you can create a launch script on Linux and include libsteam_api.so in the same folder as your binary. Note that the script must be made executable with chmod +x launch_script.sh

The "$@" passes the arguments to the script to your application

#!/bin/sh

export LD_LIBRARY_PATH="."
./your-application "$@"

[nozwock]

Definitely a lack of documentation. Take a look at my comment here for distributing your app without having to write a proxy script to setup LD_LIBRARY_PATH.
#196 (comment)