Quote:
Originally Posted by DiapDealer
I'd always get segfaults like that whenever the binary couldn't access/find the necessary Qt libraries. That's why you have to create the special launch script that adds the Qt5 libs to the LD_LIBRARY_PATH environment variable before starting Sigil.
|
And just to illustrtate that thought, here's the startup script I use (which isn't my original. I probably got it from DiapDealer or meme in the first place). It also probably isn't the only way to do it.
Code:
#!/bin/sh
## point library path and QT plugin path to Qt5 files
## for sigil Qt5 version(s).
##
## NB execute /usr/local/bin/sigil.sh instead of
## /usr/local/bin/sigil
# Entry point for Sigil on Unix systems.
# Adds the directory the Sigil executable is located
# in to the LD_LIBRARY_PATH so the custom Qt libs
# are recognized and loaded.
dirname="/opt/Qt5.0.2/5.0.2/gcc/lib/"
if [ -z "$LD_LIBRARY_PATH" ]; then
LD_LIBRARY_PATH="$dirname"
else
LD_LIBRARY_PATH="$dirname:$LD_LIBRARY_PATH"
fi
export LD_LIBRARY_PATH
## not sure if the following is necessary. But it doesn't hurt.
QT_PLUGIN_PATH="/opt/Qt5.0.2/5.0.2/gcc/lib/cmake/"
export QT_PLUGIN_PATH
exec /usr/local/bin/sigil "$@"
Instead of starting sigil directly, you execute sigil.sh instead.
And of course, the absolute paths mentioned may be different on your system. "Take notice and govern yourself accordingly."
Albert