|
If you're speaking specifically of Sigil, then "users" don't have to mess with the LD_LIBARY_PATH right now. Only packagers and knowledgeable tweakers might. In fact, in the current sigil, modifying LD_LIBRARY_PATH is unnecessary for a normal build/install (I leave it in to give me options for post-installalation diddling/repackaging). Cmake already takes care of modifying the rpath with the location of the necessary external libs (specified at build-time). The main purpose of the launch script right now, is for the setting of other env vars that allow the relocation of Sigil's support files (INSTALL_PREFIX/share/sigil), and for specifying alternative hunspell dictionaries, and for informing the Python plugin interpreter (system or bundled) where libhunspell is located so plugin devs can utilize our built-in ctypes interface to it.
|