Hi Tim,
Hope you had a nice holiday :-)
yes, thanks :-)
You wouldnt see any problems with dep
walker sinve qt image support for jpeg is via plugins. Also on your
dev system you probably wont see an issue since Qt will find the
plugins in the Qt dir.
oh, yes, what a stupid I am! I forgot to test it renaming the DevTools
folder, as I'm used to!
In fact, I did it, and the WMS loader (after connecting to the server) shows
only the PNG option
If you check main.cpp under src/app you will
see the seaerch path used for qt image plugins.
Copy the image plugins
from qtdir/plugins/imageformats/* into the qgis dir using the expected
subdir
Using Process Monitor I noticed the following failings:
C:\DEVTOOLS\QT-OPENSOURCE\PLUGINS\IMAGEFORMATS\QGIF4.DLL
C:\DEVTOOLS\QT-OPENSOURCE\PLUGINS\IMAGEFORMATS\QICO4.DLL
C:\DEVTOOLS\QT-OPENSOURCE\PLUGINS\IMAGEFORMATS\QJPEG4.DLL
C:\DEVTOOLS\QT-OPENSOURCE\PLUGINS\IMAGEFORMATS\QMNG4.DLL
C:\DEVTOOLS\QT-OPENSOURCE\PLUGINS\IMAGEFORMATS\QSVG4.DLL
C:\DEVTOOLS\QT-OPENSOURCE\PLUGINS\IMAGEFORMATS\QTIFF4.DLL
I think I should put them in the qgis/plugins, right?
I opened the cpp file and rapidly read it (I'm very short in times, sorry):
at lines 535-536 I read:
myPath += "/Contents/plugins";
QCoreApplication::addLibraryPath( myPath );
Should I create a qgis/Contents/plugins dir, or the qgis/plugins is enough?
Then, I also found the following "failings" (detected by Process Manager but
not from DepWalker):
C:\DevTools\Qt-OpenSource\bin\wintab32.dll
C:\DevTools\Qt-OpenSource\bin\ssleay32.dll
I do know nothing about wintab32.dll, while ssleay32.dll is the OpenSSL
driver... but either PgSQL nor SQLite have been compiled with the OpenSSL
support
Should I add them though? in the qgis root? at lines 537-539 of the main.cpp
I read as follows:
//next two lines should not be needed, testing only
//QCoreApplication::addLibraryPath( myPath + "/imageformats" );
//QCoreApplication::addLibraryPath( myPath + "/sqldrivers" );
interesting... but not actually compiled! (commented text). suggestions?
Finally: do you prefer a patch or a new binary release to fix that?
Regards,
Marco
_______________________________________________
Qgis-user mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/qgis-user