All the devices older than the Symbian^3 ones (N8, E7, C7, C6-01) do not have Qt installed by default. For those cases, consider using the smart installer (it is one of the Ovi Store requirements, BTW).
[quote author="butters" date="1289581791"]
Lets say I build my QT dynamic linked and then link my app against it.
Can my app still use some static linked plugins from QT by doing Q_IMPORT_PLUGIN or thats also not possible.
It's possible. Just make sure you put a CONFIG += static into the .pro file for the plugin...
[quote author="juissi" date="1289545747"]Yes, that was what I said. Also why qt_installer.sis doesn't force to C if only that works?[/quote]
The first 4.6 packages where installed on C: without prompt the user about it.
I guess it has changed due to devices where it does not fit in c: - I agree with you it should be automatically installed in C:
[quote author="Tobias Hunger" date="1289379968"]I am afraid you will now need to dive into the CMake build system![/quote]
:) Thanks again for your input! Not sure how to make this topic 'solved' but the original question is answered. I'm not going to post again, when I figured out Cmake, it's not part of the thread.
b.t.w. It doesn't matter what I need to do. Now I have a clear path and do not need to wonder am I on the right track. Plus if the original programmer(s) ever comes back, no surprises for them, they put a lot of work into this program.
It lacks information you're looking for, but it's still useful IMO. You can also improve its content providing details about not mentioned SDK versions (but then, for consistency, rather all versions should be mentioned).
I use InnoSetup on Windows. It is free even for commercial projects. NSIS doesn't have a wizard, so you have to write the script by hand. On Linux, make a .rpm / .deb package, and on Mac, use a .dmg image.
To anselmolsen: Thanks. You were right on target. As seconded by Pavanesh. It does work, even for me; the proverbial Hello program did compile just right now.
To Volker: A little known IDE called wxDev-C++. You open the environment menu, and simply choose and click, where the include files are, libraries, where your targets ought to be and so on. The IDE not in the professional class off IDEs, (neiher am I btw) but once you're done selecting, the path(s) are written into a 'make' file for any compiler you choose. Very fast, and you don't worry about a typo. I love this IDE, but unfortunately, my hobby is growing and I have to move on.
For the previously created project: As far as I know you can set the Qt version to be used afterwards, that should set the appropriate include paths.
You probably can delete the .cpp files. All of the .h files are definitely needed. But I won't do that. The disk space you gain is not that much and it's not worth the effort, IMHO. If you really want you can delete the examples subdir, but I won't do that either, because it's a good source to sneak how the trolls do certain things :-)
If you reconfigure then a generated header file, qconfig.h, will be regenerated, containing some info about what parts of Qt are enabled. That means everything which includes that header will be recompiled, which is most of Qt.
You might be able to speed up your build by using vcbuild or jom, either of which should be able to parallelize to some degree (unlike nmake).
bq. This version of PostgreSQL is not supported and may not work
So I'd suggest you try your model with an 8.x version of PostgreSQL and check if it works there. If not, it's a problem in your model. If it works, it's a problem with the 9.0 version and you'll probably have to wait until the trolls make it work.
You mentioned that you use QApplication::addLibraryPath() to add the library path. That could be the problem. That adds your plugin dir to the search path, but the default search path of Qt is still active and that could cause the system to load the release plugins.
I'd suggest you try QApplication::setLibraryPaths() or QApplication::removeLibraryPath() to get rid of the system path.