… and not only that. Qt 4.5 was also released today. Hence we decided to bundle up both Qt and QtCreator together into a “Qt SDK” that contains everything you need to begin developing with Qt.
I can say that the new Qt SDK packages containing precompiled Qt and Qt Creator for the different platforms kept some of us quite busy in Berlin the last weeks
. All of you who already tried the Qt Creator package on Windows know that we did this packaging already for this one platform, to avoid that people need to download and install mingw, and download and compile(!) Qt with mingw. But we learned that doing it for one platform is no(t so much a) preparation for doing it for all platforms and license variants:
Windows (OpenSource, Commercial, Evaluation),
Linux 32 bit (OpenSource, Commercial/Evaluation),
Linux 64 bit (OpenSource, Commercial/Evaluation),
Mac OS X (OpenSource, Commercial, Evaluation).
And we had no binary packages for Linux at all in the past…
But the result was worth the effort, every minute of it. Just go to the download page and see how it feels to get going with Qt 4.5 right away.
On the QtCreator side I’m happy to tell you that we got yet another new application icon, better following the style of the other Qt icons. I think we made the best out of it
:
And, of course, we made QtCreator available under the LGPL as well. Currently talks are going on with different packagers for Linux distributions, so hopefully you’ll be able to just press a button in your Linux distribution to get the newest Creator. All packagers who happen to read this: Please contact us, we are usually hanging around on irc.freenode.net, #qt-creator channel!
If you already used the QtCreator release candidate don’t expect too many differences – except for lots of bug fixes, crash fixes and so on. So please don’t be angry if your feature request XYZ didn’t make it into the final release. Especially since we are already hacking away for the next release, and this will not be far in the future. During the whole development time we had “release early, release often” prominent in our minds (in the very beginning doing internal releases), and this isn’t gonna to change. Though I won’t promise anything, we have something like 8 week cycles in our mind.
So just have a look at what is currently happening in QtCreator, either get the sources yourself from the open git repository (notice that you can get a .tar.gz source snapshot of the state at a certain point in time via the snapshot links), or download one of the binary snapshots we provide, which we will update to be based on the future-to-be-1.1-release.
As a last note, some of you who read Jason’s blog might ask what this strange looking building in the background of the Berlin group picture is: No, it’s not our offices. But it’s next to our offices. We are lucky to work in a historically important area, which was always a place of great (and not so great) invention and science the last hundred years. The funny spheres were thermodynamic labs with constant conditions inside of them.
Possibly related posts:

18 comments
Has anyone reported problems with using gdb debugger? Currently, a crash in my program crashes the debugger as well, the debugger does not stop at breakpoints, and other weirdness.
How can we use other build systems and debuggers with QtCreator? (vs2005/2008?)
These are all great news, but the best one is the one-click Qt SDK!
I was working on packaging Eclipse + Qt + MinGW in one NSIS Windows installer, but this SDK beats it.
Thanks for all the effort.
Some feedback regarding FakeVim
+ As a VIM user, having support for this makes me happy.
- I can’t use my beloved =G to indent all the lines in my file
- You can’t implement /text without it actually highlighting the results. Right now, it only moves the cursor to the next instance of it.
- Even if I open up the extern editor through Alt-V, Alt-I, it won’t detect the settings in my .vimrc file. It would be a huge help.
Work on these and you’ll probably attract a lot more VIM users to QTC.
I retract my previous statement about .vimrc. I forgot that this is vi world, the place where .exrc is at the roost.
Why is QtCreator unable to open files that do not have write-permissions?
I’m using Vista 64 and I can’t open any files that I don’t have write permissions for.
This also means that I can’t use F2 to jump to Qt-Symbols because I dont have write-permissions for
the Qt-Installation folder.
Could you please, please, please, please, publish information on how to make binary Linux packages? The information out there is poor, and minimal. I’ve tried several times in the past to make a binary package that will run on Linux 2.6 systems, but never succeed. It’s hard. Your expertise must be shared!
Now the only missing thing is a Linux Qt SDK which would allow you to cross compile windows code. At least setting up a cross compilation environment with 4.4.x was a pain and I couldn’t find any people who succeeded in that… (including me)
One small request: Please fix qtcreator so it can be built on non-Linux unices. Currently the “linux-*” scope is used in project files, rather than the more standard “unix”, so that it will not build on FreeBSD, OpenSolaris, etc. I cannot find anything in the code that requires Linux specificity, so I’m not sure why the decision was made to limit qtcreator.
Just a small change to the project files will make things so much easier for the rest of us. We don’t need binaries, just buildable source code. Thank you!
Why, oh why doesn’t cmd-H do anything on the Mac version of Qt Creator? Expect an angry mob of Mac users for this
When Qt Creator beta was released I put in comments configuration for dark colors in text editor. Unfortunately I overlooked some settings. Final version of this great tool is a good reason for making them better.
If you are interested, please try my dark theme for Qt Creator. I hope you’ll like it (and it will save five minutes of your life).
Wonderful product so far! I’ve been unhappy with most of the IDEs for Linux and I think I may have found one I like.
I’m currently doing some work around getting CMakeFiles to work. Is anybody else doing this? How can I help?
Drop me a line if anyone’s interested, I’d be more than happy to contribute the (extremely immature but still better than what’s there) code I’ve got so far:
agnosticTAKETHECAPSOUTpope@gmail.com
–J
Just wanted to say thanks for including the vi mode. If I am ever going to use an IDE, this would be the one.
I built qt4.5 and qtcreator on linux intrepid i386. All in path and ld config. Works great but the designer doesn’t embed. I see on the .ui text file in the editor. I have to fire up designer separate.
Thank’s a lot Qt Teams! The bug in designer (sometimes the ui class function failed to load all methods) had been fixed and help me greatly. Only “simples codes” snippet remain.
@jiaco
I have the same issue. I believe this is a compile issue as I get an error involving designer and where it says it won’t work. No idea how to resolve the issue. I guess I’ll post a solution here if I find one or you can send me an email and I can contact you that way (see my comment above).
I haven’t seen any traffic about QtCreator and distcc, is it possible?
Even if distcc isn’t possible, just getting a -j2 or a -j4 switch into the makefile (cleanly) would be a big help.
I have problems typing ü/ä and special char s like \ on german keyboard-layouts in the current snapshot from 2 days ago.
Are there any settings for that or is it a bug?
Another thing, sry: Is it possible to enable the Designer-Plugin to make the tool-objects (property explorer, object explorer…) movable and dock like in the full designer only on one side tabbed?
If not I have written a class that I could hand you to make the explorers move in and out when needed, like Windows-Task-bar. You might have a look at it. That would supply the plugin with more space for editing the forms…
Comments on this entry are closed.