Installation and Deployment

Have you tried the solution to my problem (the linked thread is mine) - Safe Mode ?

bq. To install Nokia Ovi Suite, you need: Windows XP 32-bit version (with SP2 or newer) "System requirements for Ovi Suite":http://europe.nokia.com/support/download-software/nokia-ovi-suite/compatibility-and-download Do you installed the SDK or the SP2? I suppose the SDK. The Ovi Suite can't be installed?

Where can I find info about the connection string format. All I have found at the moment is a little about using the DNS connection and setting the following: @ QSqlDatabase db = QSqlDatabase::addDatabase("QODBC"); db.setHostName( <What goes here? > ); db.setDatabaseName( < what goes here?> ); db.setUserName("xxxx"); db.setPassword("xxx"); @ Is this the right way to connect? Can I use a DNS-less connection string instead and if so how? I have set up a ODBC source on my remote server but have no idea how to connect to it.... I wont lol again, not yet anyway!

Really? I don't remember seeing syncqt run when I built Qt-4.7.2 from sources. I'll have to check later and see. Hopefully the trolls will sort this in time for Qt SDK 1.1 or 1.2.

The last time I used CentOS it really was just Fedora with the branding removed.

Created "bug report":http://bugreports.qt.nokia.com/browse/QTSDK-672 in JIRA.

"I have reported it.":http://bugreports.qt.nokia.com/browse/QTSDK-667

Amazingly simple. Thank you.

SOLVED. After Qt was rebuild with exceptions and properly tuned - program works but requires small 12 KB mingwm10.dll to support exceptions. Not a problem.

Thanks for the replies all. I wasn't aware of the shared versus static complication. So appreciate your bringing it up. I don't have any idea of the legal issues, so will leave it to the respective guys to figure it out. At the moment, I would at least like to have both static and shared linking options figured out and have a feel of the minimum sizes I can get in each case. Those numbers might also drive what licensing options we might consider. Since there is just one QT app running on our device, there is really no "need" for the shared option, except if that need is enforced upon by the licensing restrictions.

If you don't want "bleeding edge" features, branch from tag. That's what we do here : we have a public repository, and our main branch. @ git checkout v4.6.2 -b 4.6.2-Patched @ Hack, cherry-pick some changes for backport, tag, push to some public repository... When we want to port our changes to a new version: @ git pull git checkout v4.7.1 -b 4.7.1-Patched git merge 4.6.2-Patched @ Here you go, brand new version with your patches :-)

Again (mentioned this before, I believe), take a look at QFileSystemModel. It does this for you already. If you don't use it yourself, then you might study its source code to find out where it gets the images from. Or, look into QFileIconProvider. If you are using QSystemStorageInfo as your data source, then you also know which drives are a CDRom drives. Set the correct flags for those drives, and presto.

I understand that, but the sample is provided by ArcGIS, not by Qt. It is very hard to see what's going wrong based on just the linking error you give us. The ArcGIS people know what you put in the example and how it is constructed; we don't.

The Mercurial/Creator specific part has been moved to "this thread":http://developer.qt.nokia.com/forums/viewthread/4932/

Thank you so much, that perfectly solved my problem.

[quote author="eyeck" date="1301757423"]That worked perfectly... I had a feeling I was overlooking something simple like that. [/quote] No problem. That's why this forum is here. Any problem big or small will get looked at as long as the poster is polite, willing to try things and posts sensibly worded questions ;-) [quote author="eyeck" date="1301757423"] I'm sorry, I'm very new to Qt, I've been using Java Swing for years very closed-mindedly to other options. So if I were to write my own Qt Application, how would I go about generating a pro file with the necessary information? The tutorial I had been following told me -project would do the trick, apparently that isn't correct. Needless to say I am searching for a more in-depth resource to learn Qt. [/quote] Welcome to Qt ;-) [quote author="eyeck" date="1301757423"] Thank you very much for your time and responses, you've been an enormous help. I apologize for it simply being a matter of my own inexperience edit: never mind, I think I'm beginning to understand. qmake -project creates a basic pro file, which I then customize before I run qmake/make? Correct?[/quote] Yes that is correct. Qt-creator will also create you a basic .pro file when you use it to create a new project.

Yea, I would agree that it is more a Windows Server issue than Qt, I just posted the same question to Microsoft's Windows Server forum. To answer your questions, it is part of a domain, one that I control. There are no special domain policies. One extra peice of info, the machine is in a VMWare virtual machine. Sam

Thanks guys, no more question ask, everything is clear now :) thank you for your patience. cheers

[quote author="cincirin" date="1301495891"]Yes, you are right. I wanted to say resolve symbols instead of loading. About "real" windos dll I attempt to mention that a COM or ActiveX "dll" export only DllRegisterServer and DllUnregisterServer functions.[/quote] That is correct, and those are C-exports :-) Like in kernel32.dll etc.