[Psi-devel] Psi vQt4-devel + QCA2

Justin Karneges justin-psi2 at affinix.com
Sun Jan 8 08:22:29 PST 2006


On Saturday 07 January 2006 16:25, Richard Houser wrote:
> For the plug in, I have the file libqca-openssl.so in
> /usr/lib/qt4/plugins/crypto.  Was there anything special needed to
> register this with qca, etc?  I'm running the qt4 version of psi by
> changing into the darcs build directory and running the psi symlink (the
> about dialogs confirm it's the Qt4 version).

One possible problem is that the default Qt Plugin Path is wrong or 
nonexistent.  Best way to diagnose the issue would be to print out the 
QCoreApplication::libraryPaths().

[A thought: to make our lives easier in the future, maybe I'll add a function 
for this to qcatool (along with some other things perhaps, like listing the 
actual QCA plugins found).]

Anyhow, the most likely offense is that Qt is not installed into the prefix 
that it was configured for.

With Qt 3, the usual build process was to build it "in place" (ie, you unpack 
it where you want it, configure and make.  no 'make install').  With Qt 4, 
this has changed, and now Qt follows a more typical procedure by allowing you 
to specify a prefix and having a 'make install' function.  The default prefix 
is /usr/local/Trolltech or some such.  The "in place" mode is still 
available, if you set the prefix to the location of the Qt source.  Do 
'configure -prefix $PWD' and Qt will recognize it as an "in place" build.

In short, this means that if you build Qt 4 like you normally would build Qt 
3, you're going to have a messed up installation.  So maybe you want to check 
that qt4 rpm.

-Justin


More information about the psi-devel mailing list