Custom Query (301 matches)
Results (16 - 18 of 301)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #228 | fixed | qmake: Add .sym file generation | ||
| Description |
It is useful to have .sym files for all .DLLs and .EXEs since they allow to reconstruct the execution flow of a crashed application from the process dump file which is useful for analyzing crashes happening on the end user side. The .sym files should be also read by the IBM debuggers to show the symbols when stepping through the release version of the application (that does not have debugging info built in). Although it doesn't always work (I couldn't find why so far) it's better than nothing. |
|||
| #302 | invalid | qmake no longer works after yum update | ||
| Description |
By updating a system with yum, qmake no longer works. Output: sh.exe: 1: cd: can't cd to c:Projektqtkapow-1.4.4.2 |
|||
| #244 | fixed | qmake generates incorrect QMAKESPECDIR | ||
| Description |
Given that the binary Qt build is in "D:\Coding\qt4\qt4-build-rel" and the application source tree is in "D:\Coding\qt4.tests", running "qmake D:\Coding\qt4.tests" in the directory "D:\Coding\qt\qt4.tests-bin-os2" correctly gives us this: QMAKESPECDIR = "..\..\..\CODING\QT\QT4-BUILD-REL\mkspecs\os2-g++" If the application build tree is in "D:\Coding\qt\ports\1", then we get this: QMAKESPECDIR = "..\..\..\qt4.tests\CODING\QT\QT4-BUILD-REL\mkspecs\os2-g++" which is completely incorrect. This makes it impossible to have Qt in an arbitrary path. |
|||
