Installation and Deployment

It should be the same as the downloadable source package, right. If it still goes wrong, I would recommend to open a bug report on the "bug tracker":http://bugreports.qt.nokia.com

thanks for posting. but I wanna know how to compile a warning free QT library.

I've rebuilt the Qt with all packets from the "article":http://developer.qt.nokia.com/wiki/Compile_Qt_4.7_on_Ubuntu_10.10 and now I have normal appearance

[quote author="Andre" date="1300082792"] As far as I know, this layout is incorrect: the PlugIns directory doesn't belong there. Instead, the different plugin directories go directly into the application dir. At least, that is how I distribute my applications on windows, and that works. [/quote] We have to ship some other plugins too, it would clutter the toplevel directory, so we decided to put it into that subdir. An we use the QCoreApplication::addLibraryPath()[1] approach, so it does not harm. With the default settings there is too much guessing where the plugins are located, we think this is the most robust way. fn1. use this for the path: @ QCoreApplication::addLibraryPath(QCoreApplication::applicationDirPath() + "/PlugIns"); @

You'r welcome. It's great when it helped.

This is a special version to include the moc code. All QObject based classes must be processed by the moc tool ("meta object compiler":http://doc.qt.nokia.com/latest/moc.html). In regular qmake project, the moc files are added to the source file list automatically behind the scenes. The are then included in the Makefile and the object file list for the linking stage. Instead of compiling the moc generated files manually, one can #include them into a regular cpp file too. This is what happens in your case.

you can also download the Qt source package from here: "downloads":http://qt.nokia.com/downloads I think, the source package also contains the 3rd party add ons that are used

I will have to check the consistency of workflow, but I just copied the application folder as is (previously working fine) and again; the same app works fine with PNG images.

I'm new to QT so take that with a grain of salt. Here's how I got the darned thing to appropriately run configure. I'm using QT4.7.0 on WinXP Sp3 Create a user variable: QMAKESPEC = "win32-g++" Create mingw_home user variable: MINGW_HOME = "c:\qt\2010.05\mingw" <-- NO BACKSLASH!!! Add the mingw variable to my user path: Path = "...;%MINGW_HOME%\bin;" (For whatever reason the post isn't placing my percent signs in front and behind my MINGW_HOME variable.) Then restart my command prompt and run config -static inside the "c:\qt\2010.05\qt" folder. Ultimately, the ming32-make fails with the message "undefined reference to _imp_Z.... I'm going to try compiling from sources instead. I'll give more feedback later. I hope this helps someone.

Finally it worked perfectly!. Thanks so much for your support.

Already Reported as a bug : Key: QTBUG-18035 URL: http://bugreports.qt.nokia.com/browse/QTBUG-18035

Please file "bug reports":http://bugreports.qt.nokia.com/ on anything you find strange with the SDK. Getting bug reports in is the reason to have beta releases;-)

Thanks! Will try this as soon as possible :)

just another one in the qt world lol

Anyone know how I can get the deployed application to not complain about the missing QtMultimediaKit module? I've tried placing the declarative_multimedia.dll file with the application's executable, but I still keep seeing the same error.

[quote author="khalidmushtaq65" date="1299184561"] If I encrypt this database, how can I use it in QT? means what will the way to decrypt it and performing operations on the data. [/quote] Not without additional libraries. The built-in SQLite version cannot handle encrypted databases.

[quote author="Volker" date="1299070034"]Why should it not be possible? It's just another case of cross compiling. Notice, it's all about building, not running the libs :-) If you use MinGW the make command is "mingw32-make". But you need a MinGW compiler that can create 64 bit code. Probably you must install a special version of gcc, because it could be that the regular 32bit compiler does not support this cross compiling out of the box.[/quote] Thanks! I agreed Volker’s point of view: “Only build, not run.” I download MinGW-w64 cross toolchain, I not see the 32bit and 64bit command prompt, only “MinGW command prompt”. Not like VS have: 32bit: “visual studio 2008 command prompt” 64bit:“visual studio 2008 ×64 command prompt”. And unfortunately, I follow the steps of how_can_i_build_64_bit_qt_on_a_32_bit_system [developer.qt.nokia.com] , but not success. My steps: Qt Download :qt-everywhere-opensource-src-4.7.1.zip, release to D;/QT/4.7.1 Setup VS2008 (include x64 toolchain) 3: Go to “visual studio 2008 ×64 command prompt”, step into QT dir 4: Use “configure -opensource …..-platform win32-msvc2008|” the 4 step is success, but when use “nmake”, pop the error messagebox: qmake is not a valid win32 app. I know at 4 step, build 64 bit QT tools, these tools cannot running on 32bit platform. But how to build 32bit qt tools( moc.exe , uic.exe qmake.exe, rcc.exe etc.)?