History

A few years ago netlabs.org hired Dmitriy Kuminov (aka dmik) to port version 3 of the toolkit to the eCS (OS/2) platform. This port is working well and made it possible to port many applications to our platform.

Some time ago Qt 4 got introduced. New Qt applications use this version of the toolkit, of course, but also more and more existing Qt 3 applications have been making the switch. To make sure we can port those applications again, we have to invest some more work into the eCS (OS/2) port, as Qt 4 redid a lot of things from scratch. Dmitriy offered us to work on the port again. Our goal would be to hire him for about 5 months, but we cannot do that ourself without help from the community.

Sponsoring

We do have some money in the queue but it's not enough yet. If you would like to contribute to this port, you are welcome to buy a sponsoring unit for that at Mensys. 100% of that money will be transferred to netlabs.org.

Current Status

As of the 5th of February, 2010, the Qt framework version 4 for OS/2 is generally available! This means that the major parts of the Qt toolkit have been ported to OS/2 which makes dozens of Qt 4 applications potentially available to the OS/2 platform. Qt 4 for OS/2 is distributed in a convenient way using WarpIn? packages which makes it very easy to install and use it. These packages are maintained by netlabs.org and provide a so-called official build of the Qt 4 toolkit which ensures that all Qt applications use the same set of Qt 4 runtime libraries to save system resources and improve general stability. Below you will find download links to the available packages along with their descriptions.

You may find more detailed information about the project progress and future plans on the ​Roadmap page.

If you are an end-user, there already are some ​applications available for testing.

Latest Version

The latest version is 4.7.3 released on 15.09.2011. This release brings the new functionality provided by the major Qt 4.7 update from Nokia and fixes a number of bugs. This release also includes the QtDeclarative library and the awesome QML framework.

The more detailed list of changes can be found in the CHANGES.OS2​ file.

Starting from version 4.7.3, the primary way to distribute and install official binary builds of Qt for OS/2 is RPM. This means that all Qt components are provided as RPM packages which may be installed from either the netlabs RPM repositories using the YUM command or directly using the RPM command (the GUI frontend is on the way). In order to install RPM packages on your machine, you need to install the RPM bootstrap package (once) which contains the RPM installer. The installation of RPM is described ​here in detail. Once you have RPM installed, you may issue one of following commands to install various parts of Qt:

yum install libqt4

Installs the basic Qt4 runtime needed for console Qt applications

yum install libqt4-gui

Installs the Qt4 GUI runtime needed for Qt GUI applications

yum install qt4-demos

Installs the Qt Demo application that demonstrates various Qt features

yum install qt4-devel-kit

Installs the complete Qt development environment for compiling Qt applications from sources

Note that the first two commands are not normally needed -- if you install a Qt application from the RPM repository, it will install all required Qt runtime variants automatically. These commands are only necessary if you have a Qt application distributed as a ZIP archive.

Please note that you must remove all previous non-RPM installations of Qt, including the WarpIn ones, before installing any Qt RPM package! Otherwise, the new RPM installation may be incorrect or even fail.

If you accidentally forget to de-install the Qt WarpIn packages before installing one of the the Qt RPMs, then you will definitely get a broken RPM installation because the libqt4 package containing the core DLLs will fail to install (it will give you the corresponding message but it may scroll up before you can read it if you install something big like qt4-devel-kit). In order to recover from such a failure, do the following:

Remove all incorrectly installed Qt RPM packages:

yum remove '*qt4*'

De-install Qt 4 WPI packages with WarpIn.

Install the desired RPM package with yum again.

We also provide two ZIP packages of the Qt toolkit for your convenience, if for some reason you cannot use RPM. They are described below.

Prerequisites

This is a list of prerequisites for the Qt ZIP packages. Note that if you use the RPM packages, these prerequisites, except eCUPS and xsystray, will be installed automatically. eCUPS and xsystray are not in RPM repositories yet so you will need to install them from WPI in either case.

Take this if you want to build the Qt library yourself (recommended as the development environment if you regularly develop or port Qt applications).

The full Qt source code can be downloaded from the SVN repository. In order to do so you need to download and install the subversion client for eCS (OS/2) and issue the following command (<local_directory> is a directory where you want to save the sources to):

Reporting Bugs

Reporting bugs and requesting new features is done through the ticket system. You can view existing tickets, add comments to them and create new tickets using the corresponding buttons at the top of every page. If you want to submit a new bug or request a feature, please use the Search function first to make sure there is no ticket for this task already created.
We review the tickets regulary and leave comments if we need more info. So please revisit the ​Feedback analysis as often as possible. If we leave comment and don't get feedback from the ticket creator, we will close the ticket after some weeks.

Anonymous access to the ticket system has been restricted due to multiple attacks of stupid spammers we've been suffering from lately. In order to create a new ticket or comment the existing one, you need to login with your Netlabs login id.
If you do not have a login id, you can request one at ​http://www.netlabs.org/en/site/member/member.xml.
We are sorry for inconvenience, but at the present time this is the only way to avoid extremely annoying spam.

Mailing Lists

Project discussion is done through mailing list conversations. Currently, the following mailing lists are available: