[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.
As you might have noticed: The cosmetic issue is resolved in master, but unfortunately not in the 2.1 branch where we released a beta of today.
I just wanted to make sure we did not have some additional problem lurking somewhere:-)
I'm rather interested in latest minor releases of major versions, so I've just created a wiki page
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).
EDIT (2015-08-15): Fixed link.
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.
I found this link:
Is that the same stuff?
But the question is also if it is possible to get Qt Extended as LGPL and not GPL?
(that github copy seems like a GPL copy...)
i tried git clone from gitorious for the latest code, same error.
spoken with Alex Blasche at qt developer conference and he suggested that i open a bug: "http://bugreports.qt.nokia.com/browse/QTMOBILITY-688 ":http://bugreports.qt.nokia.com/browse/QTMOBILITY-688
thanks! I just need to reinstall it.
[quote author="coca-cola-planet" date="1284393552"]
you can remove it like this, those developers should add this somewhere ! like next to the download text
linuxmint ~ # cd /opt
linuxmint opt # ls
linuxmint opt # sudo ./qtsdk-2010.04/bin/uninstall
linuxmint opt #
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.
To all: Thanks for those quick responses. :D
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).
Qt already told you:
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.
My version turned out to be 4.7 in the end. The install window eventually times out (after a few hours) and provideds the option of ignoring the problem and carrying on.
After carrying on the install finished and testing a few of the providing examples seems to be all fine.
this is definitely not the right behaviour.
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.
The header files of Qt/Embedded installed to /usr/local/Trolltech/Qt-4.7.0/include,
The INCPATH in Makefile looks like:
INCPATH = -I/usr/local/Trolltech/Qt-4.7.0/mkspecs/qws/linux-x86-g++ -I. -I/usr/local/Trolltech/Qt-4.7.0/include/QtCore -I/usr/local/Trolltech/Qt-4.7.0/include/QtNetwork -I/usr/local/Trolltech/Qt-4.7.0/include/QtGui -I/usr/local/Trolltech/Qt-4.7.0/include -I. -Iinclude -I. -I.
The makefiles are all generated by qmake.
Are you trying to compile it for what architecture?
It only works for Qt for embedded linux...
[edit: fixed link / chetankjain / Gurudutt]
I believe they're important...
I did a a very fast lookup for those string:
UNICODE are being used in 3rdparty/wintab/wintab.h
QT_DLL is being used in global/qglobal.h
New you need to track down what they're doing ;)
Anyway, whatever you have to do, replicate qmake's work probably is not a good idea.
Post here your environment issues and maybe we can help you in a proper way.
It was a wrong events managment in a derivation class of QApplication, a conception error. I think, the bug just showed up at the same moment that I changed the Qt version. But there is nothing to do with version of Qt.
[quote author="Denis Kormalev" date="1285579220"]Maybe you just have .pro file with
INCLUDEPAH += .
and have someprifile.pri with
INCLUDEPAH += .
Or second "." is included from some else place.[/quote]
Your opinion is right. I tried to remove some duplicated '-I.' and still I can compile to the same result. That means the duplicated '-I.' is not necessary and could be generated by the qmake process.
Also thanks to those who provided your idea here!
marcelopaz Have you updated your Visual Studio with all the latest updates? Especially SP1?
I have found this "thread":http://social.msdn.microsoft.com/forums/en-US/vclanguage/thread/5abc3918-af6e-40e4-9962-40d90edefb1e that is about your issue however I suggest to check for updates using Microsoft Update.
OK. Managed to solve this myself. In mkspecs/common/wince/qmake.conf I simply changed the line defining the name(s) of the GLES libraries to:
QMAKE_LIBS_OPENGL_ES1 = libGLESv1_CM.lib libEGL.lib
However, this just led to another problem. When building Qt, I get a link error when linking QtOpenGLd4.dll:
link /LIBPATH:"p:\Qt\4.7.0-mobile-opengl\lib" /LIBPATH:"p:\Qt\4.7.0-mobile-opengl\lib" /NOLOGO /NODEFAULTLIB:OLDNAMES.LIB /DEBUG /SUBSYSTEM:WINDOWSCE,5.01 /MACHINE:THUMB /DLL /VERSION:4.70 /OUT:....\lib\QtOpenGLd4.dll @C:\Users\lborgne\AppData\Local\Temp\QtOpenGLd4.dll.1700.3651.jom
Creating library ....\lib\QtOpenGLd4.lib and object ....\lib\QtOpenGLd4.expqgl.obj : error LNK2001: unresolved external symbol "public: static struct QMetaObject const QGLWindowSurface::staticMetaObject" (?staticMetaObject@QGLWindowSurface@2UQMetaObject@B)
qglpaintdevice.obj : error LNK2001: unresolved external symbol "public: static struct QMetaObject const QGLWindowSurface::staticMetaObject" (?staticMetaObject@QGLWindowSurface@2UQMetaObject@B)
....\lib\QtOpenGLd4.dll : fatal error LNK1120: 1 unresolved externals
QGLWindowSurface::staticMetaObject sounds like something quite internal to Qt, and I cannot really see what could be causing it to be missing. Any ideas on how to solve this are most welcome.
I should also mention that this only happens with 4.7. 4.6.3 now builds properly with this GLES library.
Thanks you both for the quick answer. I used the tool mentioned ahead, and found that the working directory used by QtCreator was diferent than my executable. Due this I got 2 missing files.
Now I keep moving again.