Custom Query (301 matches)

Filters
 
Or
 
  
 
Columns

Show under each result:


Results (64 - 66 of 301)

Ticket Resolution Summary Owner Reporter
#179 fixed Enable support for MySQL and PostgreSQL plugins rudi
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.

#259 invalid Entry in qmake created *.pro causes Warning ak120
Description

Using qmake -project to create *.pro

By running qmake then, I got WARNING ... Unescaped backslashes are deprecated.

If manually changing appropriate line in *.pro from DEPENDPATH += ..\dirname to DEPENDPATH += . this message goes away

#165 fixed Entry input fields in Webkit don't accept some characters Silvan Scherrer
Description

in apps using the WebKit? it's not possible to enter some characters.

how to reproduce: open the Qt Demo Browser and to to www.google.com now in the searchfield enter the character @ this character is not visible

tested on a system with a swissgerman keyboard layout and lang set to de_CH. i also tryed lang en_US but still the same.

Note: See TracQuery for help on using queries.