Qt 3.1 introduces many significant new features and many improvements
over the 3.0.x series. Also lots of bugfixes.
The Qt version 3.1 series is binary compatible with the 3.0.x series:
applications compiled for 3.0 will continue to run with 3.1.
PLIST sorting.
Qt 3.0.6 is a bugfix release. It maintains both forward and backward
compatibility (source and binary) with Qt 3.0.5
Binary compatibility warning: Qt 3.0.6 is backward and forward binary compatible
with Qt 3.0.5, and is planned to be binary compatible with Qt 3.1. Unfortunately
Qt 3.0.5 is not 100% backward binary compatible with Qt 3.0.3 (a class got a few
bytes smaller), meaning executables compiled with 3.0.5 may not run properly
when linked dynamically to 3.0.3. at runtime. Note that this is not a problem on
MS-Windows. Due to its wide distributed in various GNU/Linux distributions, we
have decided to stick with 3.0.5's ABI. If you ship dynamically linked
executables, we suggest putting a QT_REQUIRE_VERSION macro at the beginning of
your main function:
...
#include <qmessagebox.h>
...
int main( int argc, char**argv )
{
QT_REQUIRE_VERSION( argc, argv, "3.0.5" )
...
}
The macro will show a message box with a warning message and then abort the
application gracefully with exit(1).
For a full buglist see the Trolltech web site.
Qt 3.0.5 is a bugfix release. It maintains both forward and backward
compatibility (source and binary) with Qt 3.0.4.
To avoid problems with loading plugins which link against different Qt
libraries, the semantics of plugin loading has been changed.
While I'm here add the PTHREAD_OPTS+=require thing to the buildlink files.
TODO: check qt3-{tools,docs} wrt buildlink2.
