If I add the codeline you write and remove my two codelines I still get one errormessage.
Qt Code:
collect2: ld returned 1 exit statusTo copy to clipboard, switch view to plain text mode
I've no idea what that error means.
If I add the codeline you write and remove my two codelines I still get one errormessage.
Qt Code:
collect2: ld returned 1 exit statusTo copy to clipboard, switch view to plain text mode
I've no idea what that error means.
Is it the only error message you get, this single line ? Aren't there any message like "undefined reference to ..." ?
Are you sure that the path to .lib file is correct ?
Be sure to remove LIBS += -lpg from the .pro file and add only the LIBS += "path/to/lib/libpg.lib".
Post the whole .pro file. Try to do a clean build as well.
Did you built the "libpg.lib" yourself ? If you've downloaded it, are you sure it's good one for your compiler ?
---
if you use QtCreator, try to scroll up in the compiler output window, maybe you just see the last line.
Last edited by stampede; 27th February 2011 at 22:09. Reason: updated contents
Yes, it's the only error message. In addition I get a warning.
Qt Code:
Qmake does not support build directories below the source directoryTo copy to clipboard, switch view to plain text mode
This is my SQL_BSP.pro file.
Qt Code:
QT += core gui TARGET = SQL_BSP TEMPLATE = app LIBS += -L"D:/Qt-Projekte/SQL_BSP/libpg.lib" SOURCES += main.cpp\ mainwindow.cpp \ postgresqldb.cpp HEADERS += mainwindow.h \ libpq-fe.h \ postgres_ext.h \ postgresqldb.h FORMS += mainwindow.ui OTHER_FILES += \ libpq.libTo copy to clipboard, switch view to plain text mode
Yes, I am sure that every file of my project is located in my specified path.
I got the lib from a friend of mine. He used it to communicate to a postgres db with a Visual C++ project (without MFC).
If it is not compatible to my compiler, where can I get the right *.lib? I've read about qsqlpsql4.dll and qsqlpsql4.lib in the web. These files are in the plugin folder of qt, but there is no header file existing. So I don't know how to use them.
Great, so you can use them - add QT += sql to .pro file and include <QtSql> in order to use Qt database framework. There are many examples how to use it in Qt examples directory, and you have nice demo of sqlbrowser implemented with Qt as well.These files are in the plugin folder of qt
Thank you for your help so far.
My SQL_BSP.pro now looks like this:
Qt Code:
QT += core gui QT += sql TARGET = SQL_BSP TEMPLATE = app SOURCES += main.cpp\ mainwindow.cpp HEADERS += mainwindow.h FORMS += mainwindow.ui OTHER_FILES += \ libpq.libTo copy to clipboard, switch view to plain text mode
I tried to get access to the sql db like this:
Qt Code:
#include <QtSql> #include <QSqlError> #include <QSqlDriver> #include <QSqlDriverPlugin> dbAlex.setHostName("localhost"); dbAlex.setPort(5433); dbAlex.setUserName("postgres"); dbAlex.setPassword("***"); dbAlex.setDatabaseName("QT"); dbAlex.open("postgres", "***"); if (dbAlex.isOpen() == true) m_sConnState = "true"; else m_sConnState = "false"; m_sConnState = dbError.text(); ui->lineEdit->setText(m_sConnState);To copy to clipboard, switch view to plain text mode
The message in my lineEdit now is "driver not loaded".
I now, I habe to work with QSqlDriver and QSqlDriverPlugin, but I have no idea how.
You can remove the OTHER_FILES += libpg.lib, because you are going to use Qt plugin for accessing database.
You have the qsqlpsql4.dll, so you should be able to use it, try to copy this file to your applications directory, or another place where windows searches for dlls.
There is a QSqlDatabase::drivers () method, it returns a list of all available drivers.
okay, I copied the "qsqlpsql4.dll" and "qsqlpsql.lib" to my project directory and added it in the *.pro file:
In my *.cpp I asked for available drivers:
The Result ist slDrivers is:
QSQLITE
QODBC3
QODBC
But no PSQL or something similar.
this line makes no sense - use -L switch when you want to add a directory to linker search path, the same I haven't noticed in your .pro file posted before:LIBS += -L"qsqlpsql4.lib"
There should be no "-L" here either.LIBS += -L"D:/Qt-Projekte/SQL_BSP/libpg.lib"
You don't have to add qt sql plugins to pro file, because you want to load them at runtime.
Try to see if the plugin is visible if you call QApplication::addLibraryPath(path) with path=<"directory with qt psql plugin"> after creating QApplication instance.
Sorry, but I'm really a beginner in Qt.
I think I need more information, about what I have to do.
Maybe it will help me if there is an easy example for using postgres with qt.
Before you can use the PostgreSQL plugin for Qt you will have to build it. Building the plugin has nothing to do with your project or its PRO file and your project does not need to link with PostgreSQL libraries directly. You only need to link to PostgreSQL libraries directly if your code uses the PostgreSQL API directly, i.e. not through the Qt Sql libraries.
Open Qt Assistant and read the page Sql Database Drivers and particularly the bit about building the PostgreSQL driver on Mac, Linux, or Windows. Just substitute the correct PostgreSQL locations for your machine in the build commands. Once the plugin is built and installed QSqlDatabase::drivers() should show QPSQL.
@ChrisW67:
The thing is that this plugin is probably already built ( qsqlpsql.dll exisits in his Qt installation ).
@WilliamSpiderWeb:
Have you tried with QApplication::addLibraryPath ? I think I've provided you with wrong info, plugins should be located in "sqldrivers" subdirectory, so it should look like:
QApplication::addLibraryPath("some path/plugins"), where "plugins" directory contains "sqldrivers" subdir (and you have psql dll file in this directory).
I hope I understood it the right way.
My main() is looking like this now:
Qt Code:
int main(int argc, char *argv[]) { a.addLibraryPath("C:/Qt/2010.05/qt/plugins/sqldrivers"); MainWindow w; w.show(); return a.exec(); }To copy to clipboard, switch view to plain text mode
But the available drivers are still the same.
The Question is, how should the software know which dll I need. It just knows where the dlls are located.
Bookmarks