Custom Query (301 matches)
Results (85 - 87 of 301)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #219 | fixed | Fix path separator when building qdoc3 | ||
| Description |
The rule to make sub-qdoc3 contains a forward slash that causes the the build process t fail. Possible fix attached. |
|||
| #289 | fixed | Fix plugin load failures | ||
| Description |
Qt core caches plugin information once it tries to load a Qt plugin. If, at this time, the plugin cannot be loaded (i.e. due to missing dependencies among DLLs), an entry saying that the plugin is invalid will be stored in the cache (and taken from there next time the plugin is loaded). This cache is not updated until the plugin DLL timestamp changes (or the cache is manually cleared). As a result, even if later all DLL dependencies are satisfied, Qt will still refuse to use it giving a message like "The file XXX.DLL is not a valid Qt plugin." This is completely wrong and needs to be fixed. It's a generic Qt problem. The workaround for this problem is to manually clear the cache entry for the plugin which is stored in %HOME%/.config/Trolltech.ini or just delete this file completely - it will be recreated next time a Qt application starts. |
|||
| #77 | fixed | Fix support for 'console' and 'windows' CONFIG flags | ||
| Description |
The 'console' flag should generate a console application (that requires standard input/output streams and a text mode window attached to it). The 'windows' flag should generate a PM application that doesn't have standard input/output or a text mode window attached. Currently, qmake passes special flags to WLINK depending on whether 'console' ("SYSTEM os2v2") or 'windows' ("SYSTEM os2v2_pm") is in CONFIG but these flags are not understood by a standalone patched WLINK version we use because system configuration files are missing. |
|||
