[qt-dev] Success building QT4 beta 3, some minor problems

[Jan van Wijk]

FYI,

I succeedded in building a working QT4 on eCS today, based on the beta-3 ZIP.
I used GCC 3.3.5 and followed the README.OS2 closely.

I had some problems, perhaps due to also having a real OpenWatcom environment,
and had to define the 'WATCON' environment variable pointing to the
location of the (QT ?) specific WL.EXE Watcom linker as in:

set watcom=h:\t

Where the 'h:\t' directory is my 'etcetera' directory for tools and utilities.

As far as I can tell that variable is always needed, so you may want
to add that to the README.OS2

After this QT4 built OK, in about 2 hours on my T42P, on a JFS partition.
I was also able to build the examples and some demos ...

Two other minor issues:

1) I tried to reach the qt.user list as mentioned on the WIKI, but get:

"No such group"

2) In the Widgets example, and also in several other examples and games,
as well as the latest SmPlayer, I saw that most (all ?) drop-down listboxes
do not seem to repaint correctly on a selection. The newly selected value
is there, but only shows after clicking on the drop-down again.
One example is the file-type/selection dropdown in a file-open dialog.

There may be a ticket open on that already, but have not found it yet :-)

Regards, Jan van Wijk

[Silvan Scherrer]

Post by Jan van Wijk
FYI,
I succeedded in building a working QT4 on eCS today, based on the beta-3 ZIP.
I used GCC 3.3.5 and followed the README.OS2 closely.

good to hear

Post by Jan van Wijk
I had some problems, perhaps due to also having a real OpenWatcom environment,
and had to define the 'WATCON' environment variable pointing to the
set watcom=h:\t
Where the 'h:\t' directory is my 'etcetera' directory for tools and utilities.
As far as I can tell that variable is always needed, so you may want
to add that to the README.OS2

i did not set that variable. i have wl in my path and it works.

Post by Jan van Wijk
After this QT4 built OK, in about 2 hours on my T42P, on a JFS partition.
I was also able to build the examples and some demos ...
"No such group"

this is known. it's not working as netlabs is not able to set it up ATM.

Post by Jan van Wijk
2) In the Widgets example, and also in several other examples and games,
as well as the latest SmPlayer, I saw that most (all ?) drop-down listboxes
do not seem to repaint correctly on a selection. The newly selected value
is there, but only shows after clicking on the drop-down again.
One example is the file-type/selection dropdown in a file-open dialog.
There may be a ticket open on that already, but have not found it yet :-)

looks like you did not search enough :) it's a combination of ticket 80
and 90 and some more small widget problems.

Post by Jan van Wijk
Regards, Jan van Wijk
---------------------------------------------------------------------

[Jan van Wijk]

Silvan Scherrer <silvan.scherrer <at> aroa.ch> writes:

<snip>

Post by Jan van Wijk
set watcom=h:\t
Where the 'h:\t' directory is my 'etcetera' directory for tools and utilities.
As far as I can tell that variable is always needed, so you may want
to add that to the README.OS2
i did not set that variable. i have wl in my path and it works.

OK, found that one. It was due to an (old) wlink.lnk in that same
directory that referenced the 'WATCOM' environment variable resulting in:

+++++++++
Warning! W1115: file wlink.lnk: line(15): environment name watcom not found
Error! E2093: file wlink.lnk: line(15): cannot open \binw\wlsystem.lnk
make[1]: *** [release\digitalclock.exe] Error 1
+++++++++

This was from my custom OpenWatcom setup that builds DOS-extended executables.

Removed that, and now it works without the WATCOM variable too :-)

Again, thanks for porting this, looks really good sofar!

Regards, JvW

[Dmitry A. Kuminov]

Hi Jan,

Post by Jan van Wijk
set watcom=h:\t
Where the 'h:\t' directory is my 'etcetera' directory for tools and utilities.
As far as I can tell that variable is always needed, so you may want
to add that to the README.OS2

No, what is actually needed (as you already found out) is to completely
remove any traces of all other [Open]Watcom installations from the
environment where you build Qt (basically, it means removing any
*WATCOM* environment variables and references to it in PATH) because
they will interfere with the custom wl.exe from Knut that we use. I'll
put this to README.OS2.

Post by Jan van Wijk
After this QT4 built OK, in about 2 hours on my T42P, on a JFS partition.
I was also able to build the examples and some demos ...

Yes, both the gcc compiler and wl.exe are sloow as nobody optimized them
for compile/link speed on OS/2 so far.

Thanks for your feedback. And feel free to ask your questions here until
the qt.user mailing list is set up.