Qt 4.8.4 / Qt Creator installation and setup grief, in both Cygwin AND Linux flavours
My employer is in the process of buying a code base which uses Qt, so I need to set up any sort of development environment that I can, in which to work examples, learn the basics of Qt, and not incidentally, refresh my C++ programming skills after most of 10 years as mostly a Java programmer.
I have two options for doing this.
- Win 7 / Cygwin
I have a Win7 PC on which I've just installed
- Cygwin 1.71 - correctly enough, that I can build a basic "Hello World" program with g++ through the Cygwin terminal (though not through a Windows terminal), and other commands like 'grep' and 'whois' work
- Qt 4.8.4 libraries for Windows, using the qt-win-opensource-4.8.4-vs2010 download (may or may not be correct)
- Qt Creator 2.6.1 for Windows, using the qt-creator-windows-opensource-2.6.1 download.
- SLES VirtualBox
On the same Win7 PC, I have Oracle VM VirtualBox running a SUSE 11 (SLES) virtual machine. I've just upgraded the Qt libraries on this machine (previously 4.7.4) to 4.8.4, using the qt-everywhere-opensource-src-4.8.4.tar (paths have also been updated in the bash.bashrc.local), and am currently trying to install Qt Creator (not previously installed) using the qt-creator-linux-x86-opensource-2.6.1.bin
Both these efforts have foundered, and I am looking for any advice anyone may be able to offer, on how to get either environment up and running.
In the Win 7/Cygwin/Qt Creator case, when I launch Qt Creator and attempt to create an empty Qt project, no surprise, it complains "no valid kits found" so I go into Options to try to set up a "kit". Under Compilers, as nothing was auto-detected (if any attempt at auto-detection was made--can't tell) I clicked Add, and when offered a drop list of MinGw, GCC, and CLang, selected GCC, and set that up with the path to c:\cygwin\bin\g++.exe. I then stepped to the CMake tab, and set that up with the path to c:\cygwin\bin\cmake.exe. I then stepped back to the Qt Versions tab, and as again there was no evidence of anything being auto-detected, clicked Add and stepped through identifying my Qt version as Qt 4.8.4(4.8.4) with the path to qmake browsed as c:\Qt\4.8.4\bin\qmake.exe ...under which I have the cheerful message, "No compiler can produce code for this Qt version. Please define one or more compilers." and a little red stop sign appears next to the "Manual" entry shown.
I have no idea what's going on here. If the Cygwin compilers I've specified aren't good enough, or there's any issue with the 4.8.4 qmake itself (?!) I have no idea how to resolve this.
In the SLES VirtualBox case, where I've reached the stage of trying to run the command:
...the output I get is:
./qt-creator-linux-x86-opensource-2.6.1.bin: /usr/lib/libstdc++.so.6: version
GLIBCXX_3.4.11not found (required by ./qt-creator-linux-x86-opensource-2.6.1.bin)
Here, I'm a bit further ahead in terms of realizing I need to find a more current libstdc++ providing this GLIBCXX_3.4.11 version--just have no idea where, or how to get it in place without breaking anything else.
BTW, I have to use Qt 4.8.4, because Qt 5 is rated as "potentially undesirable" at the company firewall and can't be downloaded. So, if installing the Qt 5 SDK would magically solve any of my problems, it's not an option.
- Win 7 / Cygwin
On windows you unfortunately need to make sure that you use one compiler for all libraries and the exectutable that links to them. You did set up a MSVC2010-build Qt and a cygwin compiler... those do not play well together. The simplest thing is most likely to install the windows SDK 7.1 (if that is still available) which comes with MSVC2010 compiler and debugging tools and use those. You can of course also rebuild Qt with your compiler, but that will most likely take longer.
Your SLES11 is unfortunately too old to be supported (it is from 2009 IIRC). I don't think there is a way to get a newer glibc onto it, as that library is pretty much the basis for everything else. Either upgrade to a newer linux (there are newer VMware images available for download on the net) or build Qt Creator yourself for SLES11. There might also be packages of Creator for SLES11 available somewhere if you are lucky:-)
Another day of head-banging around this problem has produced the following solutions...
In the SLES case, patching up to Service Pack 2 pulled in a 4.0.something glibc, which exceeds the Qt Creator 2.6.1 requirement for 3.4.11. This has allowed me to get the .bin installed and go forward with this as my primary Qt study zone.
In the Win 7 case, after several abortive attempts to get the SDK 7.1 installed, I installed the Qt 4.6.4 mingw package with a download of MinGW, and was able to get Qt Creator going with that. I'm still working on the SDK installation as a separate project, and will see if I can get that supporting 4.8.4 once done, but this can now mercifully step down to being a less than essential exercise.
Thanks for the info, it has been a help!
I am also trying to install Qt-5.1.0(latest) on SLED(suse linux enterprise desktop) but i am not able to running qtcreator after installing Qt .
While running time i am getting errors. Can you see following Qt posts here you can observe what is problem.
All are suggesting compile Qt source code, but while compile time also getting issues.
I think you have already succeeded with Qt-4.8.4 but for me that is also failed same error getting as i got while running qt-5.1.0.
Can you please help me to run any version of Qt on Suse linux enterprise Desktop 11