Quote:
Originally Posted by KevinH
Hi,
If you are a Linux user that is seeing this doubling of issue please do the following in a bash shell.
cd (to where ever you actual sigil executable binary is located on your machine)
then
ldd sigil
This should tell us exactly which files the Sigil executable will be using.
Thanks,
KevinH
|
That won't work for users of my binary package (or for the usual 'make install build'). /usr/local/bin/sigil is a script that sets the LD_LIBRARY_PATH and the proper plugin launcher env vars before launching the actual sigil executable that has been relocated to /usr/local/share/sigil. That way the executable is in the same directory as the Qt5 libs/plugins (binary package version).
They'd need to do something like:
Code:
LD_LIBRARY_PATH=/usr/local/share/sigil ldd /usr/local/share/sigil/sigil-real
I
have confirmed the doubling entity issue, now, (by creating a Debian Wheezy VM). There is no other Qt5 libs on the system and ldd confirms sigil is using the Qt5.4.0 that I've distributed with the package. I'm going to try and build Sigil on Wheezy to see if that makes a difference.