MySQL/MariaDB connector driver building Qt 6 Windows 10
-
You have to make sure all needed depent dlls are in the PATH.
@Christian-Ehrlicher said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
You have to make sure all needed depent dlls are in the PATH.
And how can I identify which dlls are depent? I know how to check the PATH variables
-
@Christian-Ehrlicher said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
You have to make sure all needed depent dlls are in the PATH.
And how can I identify which dlls are depent? I know how to check the PATH variables
E.g. with DependencyWalker or it's successor Dependencies. You need at least the mysql or mariadb dlls
-
E.g. with DependencyWalker or it's successor Dependencies. You need at least the mysql or mariadb dlls
@Christian-Ehrlicher said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
E.g. with DependencyWalker or it's successor Dependencies. You need at least the mysql or mariadb dlls
I have each one in their specific connectors. Apart from there should I copy these dlls, into another folder?
-
@Christian-Ehrlicher said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
E.g. with DependencyWalker or it's successor Dependencies. You need at least the mysql or mariadb dlls
I have each one in their specific connectors. Apart from there should I copy these dlls, into another folder?
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
Apart from there should I copy these dlls, into another folder?
You have to make sure all needed depent dlls are in the PATH.
-
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
Apart from there should I copy these dlls, into another folder?
You have to make sure all needed depent dlls are in the PATH.
@Christian-Ehrlicher said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
Apart from there should I copy these dlls, into another folder?
You have to make sure all needed depent dlls are in the PATH.
I used the prebuilt .dlls from here https://github.com/thecodemonkey86/qt_mysql_driver
And then followed without any error the commands forMSVC2019, nothing worked. In the end the Driver is available but not loaded.
As you can see in the following images, I have set the libmariadb.lib in enviroment variables and /lib and /include subdirs into PATH.
Finally the dependecies for qsqlmysql.dll are fulfilled since I have compiled with MSVC
What is the next step :p. Iam feeling silly since I follow all the steps and stills doesnt work -
YESSSSSSSSSSSSSSSSS FINALLY WORKED. I copied libmaria, qmysql, qmysqld dlls into
C:\Users\panos\AppData\Roaming\Python\Python310\site-packages\PyQt6\Qt6\plugins\sqldrivers -
YESSSSSSSSSSSSSSSSS FINALLY WORKED. I copied libmaria, qmysql, qmysqld dlls into
C:\Users\panos\AppData\Roaming\Python\Python310\site-packages\PyQt6\Qt6\plugins\sqldrivers@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
qmysqld
This one is the debug version and I don't think you need it as you're probably not going to debug it.
-
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
qmysqld
This one is the debug version and I don't think you need it as you're probably not going to debug it.
@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
qmysqld
This one is the debug version and I don't think you need it as you're probably not going to debug it.
I thought that mysqld.dll has to do with mysqld.exe, because now Iam wondering, how my database could wok in another computer, where no mariadb server etc. files are installed, so we would like to have the mysqld.exe ''representative''
-
@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
qmysqld
This one is the debug version and I don't think you need it as you're probably not going to debug it.
I thought that mysqld.dll has to do with mysqld.exe, because now Iam wondering, how my database could wok in another computer, where no mariadb server etc. files are installed, so we would like to have the mysqld.exe ''representative''
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
mysqld.exe
What is this?
Clients do not need the server stuff, just deploy client libraries together with your application.And to precise what I mentioned before:
- qmysql.dll - this is the release build of the plug-in
- qmysqld - this is debug build of the plug-in
There is really no need to deploy release AND debug build of the plug-ins/libraries.
-
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
mysqld.exe
What is this?
Clients do not need the server stuff, just deploy client libraries together with your application.And to precise what I mentioned before:
- qmysql.dll - this is the release build of the plug-in
- qmysqld - this is debug build of the plug-in
There is really no need to deploy release AND debug build of the plug-ins/libraries.
@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
mysqld.exe
What is this?
Clients do not need the server stuff, just deploy client libraries together with your application.And to precise what I mentioned before:
- qmysql.dll - this is the release build of the plug-in
- qmysqld - this is debug build of the plug-in
There is really no need to deploy release AND debug build of the plug-ins/libraries.
I understand your point, but what if I want to distribute my app to another computer and this computer does not have any db server installed. Could the database connect and work successfully only with client libraries even if none dbms server software is installed?
-
@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
mysqld.exe
What is this?
Clients do not need the server stuff, just deploy client libraries together with your application.And to precise what I mentioned before:
- qmysql.dll - this is the release build of the plug-in
- qmysqld - this is debug build of the plug-in
There is really no need to deploy release AND debug build of the plug-ins/libraries.
I understand your point, but what if I want to distribute my app to another computer and this computer does not have any db server installed. Could the database connect and work successfully only with client libraries even if none dbms server software is installed?
@paokaras98 Well, of course there should be a server reachable from the client, so client can connect to it. But a client application should not distribute the server.
The client itself only needs client libraries to connect to a server. -
@paokaras98 Well, of course there should be a server reachable from the client, so client can connect to it. But a client application should not distribute the server.
The client itself only needs client libraries to connect to a server.@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 Well, of course there should be a server reachable from the client, so client can connect to it. But a client application should not distribute the server.
The client itself only needs client libraries to connect to a server.Ok I got your point. However, suppose I have a customer to sell my software and this customer does not want to mess up with installations. He wants only an all-in-one installer to install the app and the dependencies(in my case the dbms server). So the dbms server .msi should be somehow included to my final installer and executed... am I right?.
-
@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 Well, of course there should be a server reachable from the client, so client can connect to it. But a client application should not distribute the server.
The client itself only needs client libraries to connect to a server.Ok I got your point. However, suppose I have a customer to sell my software and this customer does not want to mess up with installations. He wants only an all-in-one installer to install the app and the dependencies(in my case the dbms server). So the dbms server .msi should be somehow included to my final installer and executed... am I right?.
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
So the dbms server .msi should be somehow included to my final installer and executed... am I right?
Yes, but this has nothing to do with your client application.
-
@jsulm said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
@paokaras98 Well, of course there should be a server reachable from the client, so client can connect to it. But a client application should not distribute the server.
The client itself only needs client libraries to connect to a server.Ok I got your point. However, suppose I have a customer to sell my software and this customer does not want to mess up with installations. He wants only an all-in-one installer to install the app and the dependencies(in my case the dbms server). So the dbms server .msi should be somehow included to my final installer and executed... am I right?.
@paokaras98 said in MySQL/MariaDB connector driver building Qt 6 Windows 10:
Ok I got your point. However, suppose I have a customer to sell my software and this customer does not want to mess up with installations. He wants only an all-in-one installer to install the app and the dependencies(in my case the dbms server). So the dbms server .msi should be somehow included to my final installer and executed... am I right?.
Thank your for your clarification. I will make my research now
