Migrating development XD

[chaosgeorge]

ok so i need to install mysql libraries dont i ? i only need the sources and add the path to the dependencies? or better placing the dependencies in the executable directory?
thanks

[budul]

As you need. It depends on you where you put additional mysql libraries. But ensure that you fulfil all needs of your plugin. And be aware of release/debug mix as Jacek mentioned. Good luck.

[chaosgeorge]

guess what, i get a driver not loaded message, i managed to compile with plugin but running it i get that, i checked the plugin's dependencies with dependency walker and i got everything ok, so any suggestions? thanks

btw do i need to add a path to some mysql directory in env vars?

[chaosgeorge]

ok it looks like qsqlmysql plugin does not need any libraries that come with the source of mysql, however to work with the Qt 4.2.1 i had to remake the plugin as I did with my home's 4.2.0, i dont think there is incompatibility with Qt versions because the plugin made in the 4.2.1 machine worked fine with my 4.2.0 at home, but i dont want to remake the plugin wherever i port my app, what could be the problem that i had to remake the plugin to work? mingw incompatibility? Qt? mysql drivers?

[jacek]

One of the possible explanations it that Qt adds a "build key" to plugins and it refuses to load them if their key differs from the library key.

http://doc.trolltech.com/4.2/plugins...#the-build-key

[jacek]

ok so i need to install mysql libraries dont i ? i only need the sources and add the path to the dependencies? or better placing the dependencies in the executable directory?

IMO the safest way is to copy MySQL DLLs to the same directory where you executable is (note that the QMYSQL plugin itself has to be in a "sqldrivers" subdirectory).

You can use Dependency Walker to check what MySQL DLLs that plugin needs, but beware that it might require more DLLs, as these can be loaded in the runtime.