3 ms·
> On Linux it's not quite as nice since you have to move the libsciter.so to the appropriate folder. Incorrect. Linux doesn't care where you load a .so from. Y
by pritambaral 4y ago
> On Linux it's not quite as nice since you have to move the libsciter.so to the appropriate folder.
Incorrect. Linux doesn't care where you load a .so from. You could load it by using a path, or you could add a path to your LD_LIBRARY_PATH env var. You could even add it to your compiled binary's RPATH. All methods support relative paths. The latter requires a binary, but the first two work with nearly all scripting languages.
- pessimizer 4y agoNone of those options are any easier than moving it. No harder, but no easier.
- jjnoakes 4y agoThey are easier for the end user in certain cases. Putting the library in the system library search path requires elevated privileges (usually). Having your application run from a self-contained directory does not.
- electroly 4y agoI don't think I agree. You don't need root and you don't need to "install" anything with these other options; it allows the user to extract and run rather than extract, elevate, install, run. It clearly shifts some of the pain from the user back to the developer. It's particularly clearly a win if you're distributing your app on your website instead of via distro package managers.
- ptspts 4y agoA shell script provided by the app author can automate setting LD_LIBRARY_PATH and running the binary. It's very convenient for the end user. Lots of programs are shipped to Linux this way.