Sometimes even a Tech Preview or Beta of the QtSDK or QtCreator seems too far behind, especially when you see that something that bugs you has already been resolved in the mystical master branch. My favourite is for example that I can start my Maemo apps without going through the packaging step. If you are in similar shoes, and you (and your projects) are not afraid to be mentally traumatized, cut and maimed by the bleeding edge (you have been warned !), you can always grab the stuff from gitorious. Except, building QtCreator can be a drag, especially if you're not on per tu with gitorious. This brings us to the crux of the matter:
The QtCreator nightlies
Yes, I pretty much made a blog post and a long intro just to give you this link - lame, I know :) You have Windows, Mac, Linux32 and Linux64 binaries there. Note that sometimes a particular platform might be missing due to build failures - in that case just go ../ from the latest directory and check previous day or two. The general advice is to install the nightly in a different directory (i.e. not within the QtSDK). A special note is that QtCreator keeps some of it's settings as global, which is a double-edged sword - on one hand it makes easier to use the same Qt versions and rootstraps in both the stable and nightly QtCreators, but also can lead to config pollution if going back-and-forth between various versions which might require an SDK reinstall (you have been warned - again !).
Keep the Qt applications flowing and have Qt fun(k) !
The QtCreator nightlies
Yes, I pretty much made a blog post and a long intro just to give you this link - lame, I know :) You have Windows, Mac, Linux32 and Linux64 binaries there. Note that sometimes a particular platform might be missing due to build failures - in that case just go ../ from the latest directory and check previous day or two. The general advice is to install the nightly in a different directory (i.e. not within the QtSDK). A special note is that QtCreator keeps some of it's settings as global, which is a double-edged sword - on one hand it makes easier to use the same Qt versions and rootstraps in both the stable and nightly QtCreators, but also can lead to config pollution if going back-and-forth between various versions which might require an SDK reinstall (you have been warned - again !).
Keep the Qt applications flowing and have Qt fun(k) !
Please note that the snapshots are from the 2.1 branch of Qt Creator at this time and not of the master branch! They will be switched back after 2.1 is released.
ReplyDelete