Custom Query (301 matches)
Results (70 - 72 of 301)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#232 | fixed | Missing QtCore exports | ||
Description |
Attempting a full rebuild (no shadow) fails when linking QtXml? due to missing exports from QtCore?. Several symbols (like QByteArray::QByteArray(const char *) are not exported anymore. The newly created QtCore?.lib is smaller than it used to be. Shadow build fails even earlier. QMake can't be built due to missing include path (qstringlist.h not found). |
|||
#233 | fixed | Wrong executable location for debug_and_release | ||
Description |
When rebuilding a project the uses debug_and_release (non-shadow), I noticed that the executable and *.SYM file ended up in the current (i.e. the source) directory. With previous versions (as well as on Windows), the executables are created in the debug and release subdirectories. The current makefile.xxxx section looks like this: QMAKE_TARGET = DoseControl DESTDIR = TARGET = DoseControl.exe DESTDIR_TARGET = DoseControl.exe while previous versions of QMake created: QMAKE_TARGET = DoseControl DESTDIR = release #avoid trailing-slash linebreak TARGET = DoseControl.exe DESTDIR_TARGET = release\DoseControl.exe |
|||
#234 | fixed | QtCreator's qmlpuppet doesn't get installed | ||
Description |
The utility qmlpuppet doesn't have an install target (multi-platform bug). In my case this caused it to be missing when building a binary distribution package. This caused Qt Creator to hang when switching back and forth between text graphical editors (QmlDesigner?). Dmik, could you please check what happens in our QProcess implementation when the required executable is missing ? To me it looked like something in the pipes mechanic blocked, making Qt Creator unkillable. |