PostgreSQL client Windows Deployment Nightmare "Driver Not Loaded"
-
Hi,
You wrote about both MSVC2013 and 2015 so are you trying to use a MSVC2013 build of PostgreSQL with a MSVC2015 build of Qt ? If so that won't work, Microsoft's compilers are not compatible one with the other when building C++ libraries. The current only exception is VS2017 which is backward compatible with VS2015. So beside architecture also check that part.
Note that it looks like you are trying to distribute a debug build which might not be what you want.
-
Hi,
You wrote about both MSVC2013 and 2015 so are you trying to use a MSVC2013 build of PostgreSQL with a MSVC2015 build of Qt ? If so that won't work, Microsoft's compilers are not compatible one with the other when building C++ libraries. The current only exception is VS2017 which is backward compatible with VS2015. So beside architecture also check that part.
Note that it looks like you are trying to distribute a debug build which might not be what you want.
Hello @SGaist
I'm not trying to distribute debug version.. I can only have that output at Debug mode.. After making lots of trial and new test projects..
I found that problem couse from a global QSqlDatabase variable.. That cost me a week...
It tries to create it self before QCoreApplication so no plugins can be loaded..Thanks to Everyone...
Linux Mint 20.04 64 Bit QT6.0.1
-
Hello @SGaist
I'm not trying to distribute debug version.. I can only have that output at Debug mode.. After making lots of trial and new test projects..
I found that problem couse from a global QSqlDatabase variable.. That cost me a week...
It tries to create it self before QCoreApplication so no plugins can be loaded..Thanks to Everyone...
Oh
That was a nasty one.
There were no errors/warnings in Creator console? -
@zeroptr
Yep there is a many very good reasons most of us avoid globals at all costs.
But normally there is a warning that object initialized before application running
sort of msg.
Update:
Nope, did not say a thing.Normally u get
-
There's absolutely no need for a class member nor a global QSqlDatabase variable. It's already a sort of singleton that has all the interface needed to retrieve database information any time needed.
-
@zeroptr
Yep there is a many very good reasons most of us avoid globals at all costs.
But normally there is a warning that object initialized before application running
sort of msg.
Update:
Nope, did not say a thing.Normally u get
-
There's absolutely no need for a class member nor a global QSqlDatabase variable. It's already a sort of singleton that has all the interface needed to retrieve database information any time needed.
-
To be fair, there's a warning in the detailed documentation of QSqlDatabase about not keeping QSqlDatabase variables around.
Interested in AI ? www.idiap.ch
Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct -
@mrjj unfortunately if I get this message before I can repair this in a day or two.. but mingw or MSVC doesn't produce any message like this..
@zeroptr
Well it didn't say that for the QSqlDatabase .
Only the QWidget gave spank at once.
I guess its not illegal to have an instance of QSqlDatabase
before main but as you found out it can that try to use stuff
before its up and running.But the good part is that we learned something. I didn't guess at such thing but next time i will ask.
-
To be fair, there's a warning in the detailed documentation of QSqlDatabase about not keeping QSqlDatabase variables around.
