All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
changes (among many others):
- New QLocale Class
- The ActiveQt framework, first available in Qt 3.1, has been enhanced in
lots of ways in Qt 3.3.
- Semi-Transparent Windows
Other Improvements
- The network module now supports IPv6 in addition to IPv4.
- New 64-bit platforms are supported: Itanium on Linux (Intel compiler) and
Windows (MSVC and Intel).
- QCursor now provides the BusyCursor shape, which combines an hourglass with
an arrow.
- Qt's DOM classes are now reentrant when Qt is built with multithread support
enabled.
See http://www.trolltech.com/products/qt/whatsnew.html for more details.
Far too many new features and bug fixes to list here. Includes a fix for
Hangul (Korean character) handling from Bang Jun-Young <junyoung at netbsd
dot org>. Thanks.
"Better late than never"
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.
buildlink2.mk files back into the main trunk. This provides sufficient
buildlink2 infrastructure to start merging other packages from the
buildlink2 branch that have already been converted to use the buildlink2
framework.
o Enable thread support using pth-syscall and nathanw_sa. The
later has problems which are being worked on.
o Restructure the build of certain plugins so that qt3-libs
comes with jpeg and mng support.
o Introduce a BUILDLINK_DEPENDS_METHOD.qt3-tools variable that
when set to build means we don't get a full dependency on
qt3-tools.
