Custom Query (301 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (100 - 102 of 301)

Ticket Resolution Summary Owner Reporter
#125 fixed QMAKESPEC qmake variable not defined Dmitry A. Kuminov
Description

Outside the Qt source tree, the QMAKESPEC qmake variable is not defined but we refer it in the default_post.prf file for the OS/2 platform. As a result, the BLDLEVEL info taken from VERSION, QMAKE_TARGET_PRODUCT and other similar variables cannot be generated because emxexpw.cmd necessary for that is not found.

#126 fixed Building projects with "dev" WPI package fails Dmitry A. Kuminov
Description

Building some qmake-based projects with the "dev" WPI package fails like this:

g++ -Zomf -Zstack 0x2000 -Zlinker "DISABLE 1121" -s -Zhigh-mem -Zmap -o widget.exe . \widget.exe.def @d:\Temp\widget_tes
t\OBJECTS.widget.rsp -Lc:\ECS\SYSTEM\QT4\lib -lQtGui4 -lQtCore4
g++: \widget.exe.def: No such file or directory
#127 fixed QDesigner fails to load large/complex ui file made on MAC/Windows jvw
Description

I just installed the Qt4 4.51 WPI archives to check out QDesigner with some existing Qt projects I have (created on Windows, using Qt 4.60).

Sofar I did not install the GCC compiler yet, just playing with the designer.

The very first project I tried, with one dialog, failed to load that dialog with an error message stating the file was not a valid ui file, with additional info saying:

++++++ An error has occurred while reading the ui file at line 1, column 2: Expected '?', '!', or '[a-zA-Z]', but got '/'. ++++++

Of course those lines look fine in an editor, and the files works fine on Windows as well as the MAC. A small dummy dialog created on OS/2 does read back properly.

Testing the larger dialog by removing several widgets from the ui file, lead me to believe there is some size constraint (or overflow bug). After removing checkboxes one-by-one, the file became 'acceptable' when 4 of the 8 checkboxes had been removed, and the file size went down from almost 9884 bytes to 8376.

I will try to attach an OK and BAD version of the ui file.

TIA for any insight on this problem ...

Jan van Wijk

Note: See TracQuery for help on using queries.