Custom Query (301 matches)
Results (37 - 39 of 301)
Ticket | Resolution | Summary | Owner | Reporter |
---|---|---|---|---|
#178 | fixed | Poor QNetworkDiskCache performance | ||
Description |
Not sure if we should do this kind of things, because it's a multiplatform issue. Even though it probably hurts most on OS/2 (see also #176). Find attached a patch to improve the performance of QNetworkDiskCache::expire(). It avoids to stat() cache files before they get deleted. It sees to futher improve Arora browser's behavior. |
|||
#179 | fixed | Enable support for MySQL and PostgreSQL plugins | ||
Description |
It turns out, that these two database plugins can be build quite nicely. We should at least offer "configure" support for them (if not even ship binary versions). Here is, what I did to compile them: Added to src\plugins\sqldrivers\mysql\mysql.pro os2 { TARGET_SHORT = qmysql LIBS += -lmysqlclient_r -lpthread -llibssl -llibcrypto } Then run: qmake "INCPATH+=<mysql_path>\include\mysql" "LIBPATH+=<mysql_path>\lib" make I couldn't find a clear statement, if the "reentrant" version of the MySQL client library is really necessary when used in the context of a Qt plugin. If not, it would remove the dependency from pthread. For PostgreSQL the change in src\plugins\sqldrivers\psql\psql.pro could look like this: os2 { TARGET_SHORT = qpgsql LIBS += -llibpq -llibssl -llibcrypto } And the qmake/make command being similar. In both cases the resulting plugins depend on OpenSSL. I'm not sure, if we should make the selection of the SSL libs a config option so that the user can also build the plugins with SSL linked in statically. But as I wrote in #167, I would prefer the DLL approach. BTW, I did a quick test only with MySQL. I don't have PostGreSQL running here. |
|||
#180 | wontfix | Location of ui_*.h | ||
Description |
With 4.6.3, qmake places the generated ui_*.h files in the objects directory. While appears to be a good choice not to mix the generated files with the source, it caused a compile break here. In order to fix this, I had to add "." to the compiler's include path. Is that working as designed ? |