Do you want to know how your customers use your applications and devices? Try Qt Insight Beta.
最新版Qt 6.3已正式发布。 了解更多。
最新バージョンQt 6.3がご利用いただけます。 詳細はこちら

Qt 4.6.0 Release Candidate 1

Today, we move another step closer to the Qt 4.6.0 release, with the shipping of the first release candidate.

This release improves on 4.6.0 Beta 1 by adding yet more bug fixes and documentation improvements, fine-tuning a couple of the new API's, and incorporating various feedback from you, Qt's community of developers and users.

The Release Candidate is very close to what the final 4.6.0 release will be. The main aim of the RC is to solicit feedback from the community and catch any remaining high priority bugs before the final release, which we expect will happen before the end of the year.

If you find a bug, we want to hear about it. You can submit a bug report and/or an autotest that demonstrates the bug via the public Qt Bug Tracker. If you know how to fix the bug, you can submit a merge-request to the public Qt source repository on http://qt.gitorious.org.

The Release Candidate is available as a source package (choose from .tar.gz and .zip versions), and as pre-built binary packages for Windows, Mac OSX (Carbon and Cocoa) and Symbian. In addition to the set of binary packages shipped with the Beta, we are now providing an opensource version of the Visual Studio 2008 binary package.

You can get all of the packages from the Qt Preview Website, or from our http://get.qt.nokia.com. You can also find the latest documentation at http://qt.nokia.com/doc/4.6-snapshot/index.html.

Finally, a note for users of the MinGW binary package: This package is now based on MinGW 4.4. The installer no longer offers to download MinGW for you, but rather offers to use a version of MinGW that you already have installed on your machine. You just tell the installer which directory MinGW is installed in.

If you don't already have MinGW 4.4 installed, you can download a .zip archive from our ftp site. This archive provides fixes to MinGW and support for missing API, See the _patches directory in the archive for details.


Blog Topics:

Comments