I certainly appreciate hearing that others have experienced the same bug, it still doesn't detract from the fact that it is a bug. Windows users experience the blue screen of death on a fairly regular basis, and some may consider that normal behavior, but that doesn't mean it's not a bug - because it is.
I'd like to know how to at least find out what can be done to make Qt Designer and Qt Assistant fully functional on a Windows platform, because clearly the way the "Maintain Qt SDK" functions causes the packages to NOT be fully functional.
[quote author="pmjz" date="1318875676"]bq. MinGW is the default build on Windows. If there is no MinGW toolchain you most probably just didn’t install them. Open the SDK maintenance utility and make sure you’ve installed them.bq.
my friend, are you sure? [/quote]
Well, it looks like I was right, wasn't I?
Just fire up your Qt SDK maintenance utility and tick the Desktop Qt 4.7.4 - MSVC 2008 package. The compiler comes with an VisualStudio 2008 Express edition or the Windows SDK (don't ask me about the licensing restrictions).
[quote author="tomi127" date="1318540350"]@If somebody can't build MySQL you CAN'T use MySQL C++ Connector.[/quote]
What do you mean ? I use only "My SQL Connector/C++":http://www.mysql.com/downloads/connector/cpp/. It works with both VC and MinGW compilers.
[quote author="Volker" date="1318421919"]There is no universal Cocoa and Carbon in Qt world. You have either one or the other (depending on the command line switch you feed to the configure script during the build of Qt).
I guess I am misunderstanding the docs then, because in 'Developing Qt Applications for Mac OS X' page, the 'Which One Should I Use?' section says I can have 'a 64-bit Cocoa and 32-bit Carbon universal application'. If this is in fact not the case, I'll try reconfiguring my Qt with -carbon, and perhaps log a bug against the documentation.
That aside, I am still not convinced the missing symbol is anything to do with which architecture I am targeting, but more of an SDK issue, but searching Google isn't helping pin it down.
I'll probably report back with success or failure once Qt has rebuilt, which will be a while on my Mac Mini.
This has been discussed so many times before, here. Please refer to the following older threads on the very same topic:
Tag search: http://developer.qt.nokia.com/search/tag/installer
Thank's for the compliment, but I learned the hard way, having had the exact same problem some years ago. It took me a day or two to find out a decent solution. So it's only fair to share my experiences to save you from the manifest fiasco - the successor of the DLL hell :)
Thanks fot the tip. Still not resolved though. My imports folder (imports/Qt/labs) now has both components and components.1.1 in it.
From my QML I manage to run with:
@import Qt.labs.components.native 1.0@
Now the question is how can I reference 1.1? And also, do I need to? Is this a newer version of the existing components?
I can't compile
@import Qt.labs.components.1.1 1.1@
or other variations I tried.
OK, sth is wrong indeed. in a hello directory consisting of hello.cpp and hello.pro i go with
@qmake -spec macx-g++@ and the little gui (hello.app) builds fine, whereas with
@qmake -spec macx-xcode@ i get a hello.pbproj and the related plist without any Xcode directory.
i 'll build qt from scratch, thanks
It is not recommended to build Qt manually from the sources provided by the SDK. As a first step you must download the vanilla sources from "Qt download site":http://qt.nokia.com/downloads/downloads#qt-lib, then follow the steps described in the wiki.
4 MB for a statically linked hello world executable, which includes Qt lib stuff and C++ stdlib stuff, is not huge!
Leaving out some features in a static build does not reduce the size of the final executable in a noticeable way. By linking statically against the Qt libs, you will pull in only the object code that is needed to run your app.
No. On another machine you need to have the Qt 4 libs available, either by providing it yourself or by using a preinstalled version of the system.
For a .deb or a .rpm, you usually will not pack the Qt libs into the installer but set a dependency, so that another package will be installed automatically ifs contents are missing.
[quote author="Peppy" date="1317243089"]so? No idea?[/quote]
Please stop bumping topics in that short time. We do not sit before the screen and wait for updates to answer on.
From my experience, the VS redistributable exe (vcredist_x86.exe) can be executed many times without problems (at least up to VS2005, I will try with VS2008 soon). If you put it into an installer (like InnoSetup), you can start a silent installation with this call:
vcredist_x86.exe /q:a /c:"msiexec /i vcredist.msi /qn /l*v %TEMP%\vcredist_x86.log"
(again, tested with the VS2005 version)