No matching signals for all controls
-
@mrjj Correct
@Deathcomes
I have no idea why then it must not seem then when running
QMetaObject::connectSlotsByName(Widget); -
New info on the problem!
The failing auto connection of the signals happen when i add the -lQt5Ftp library on
LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32which i built from this https://github.com/qt/qtftp
I tested it with creating a new empty qt project (window application) and adding only one button and slot (with right click -> goto slot "clicked"). Inside the slot i added a
qDebug() << "Click";Built/run on debug mode and everything runs smoothly (the slot is connected and fired properly)
Then i add the above line inside the .pro file and Rebuilt the project from scratch. When i run the application i got the usual warning
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()and the slot is not fired.
I also tested if the library -lKernel32 was the problem but everything executed fine when i left only this library. -
New info on the problem!
The failing auto connection of the signals happen when i add the -lQt5Ftp library on
LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32which i built from this https://github.com/qt/qtftp
I tested it with creating a new empty qt project (window application) and adding only one button and slot (with right click -> goto slot "clicked"). Inside the slot i added a
qDebug() << "Click";Built/run on debug mode and everything runs smoothly (the slot is connected and fired properly)
Then i add the above line inside the .pro file and Rebuilt the project from scratch. When i run the application i got the usual warning
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()and the slot is not fired.
I also tested if the library -lKernel32 was the problem but everything executed fine when i left only this library.@Deathcomes
That is really odd as that's a lib and should not really
interfere with moc and signal findings.
Maybe it screws up the meta data somehow. -
@Deathcomes
That is really odd as that's a lib and should not really
interfere with moc and signal findings.
Maybe it screws up the meta data somehow.@mrjj said in No matching signals for all controls:
Maybe it screws up the meta data somehow.
How can i check it?
-
@mrjj said in No matching signals for all controls:
Maybe it screws up the meta data somehow.
How can i check it?
@Deathcomes
I dont know if we can see that.
we can check what connectSlotsByName
does here
https://code.woboq.org/qt5/qtbase/src/corelib/kernel/qobject.cpp.html#3539maybe we could dump the names it sees with and without ftp lib.
-
New info on the problem!
The failing auto connection of the signals happen when i add the -lQt5Ftp library on
LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32which i built from this https://github.com/qt/qtftp
I tested it with creating a new empty qt project (window application) and adding only one button and slot (with right click -> goto slot "clicked"). Inside the slot i added a
qDebug() << "Click";Built/run on debug mode and everything runs smoothly (the slot is connected and fired properly)
Then i add the above line inside the .pro file and Rebuilt the project from scratch. When i run the application i got the usual warning
QMetaObject::connectSlotsByName: No matching signal for on_pushButton_clicked()and the slot is not fired.
I also tested if the library -lKernel32 was the problem but everything executed fine when i left only this library.@Deathcomes
One question: why is something as old as Qt 5.2 involved in your build? -
@Deathcomes
One question: why is something as old as Qt 5.2 involved in your build?@JonB We started development on that version and there was never a necessity to upgrade to a newer version.
-
It seems (again!) that the problem indeed wasn't the qt5ftp library but the way i built it.
You see we use dynamic linking for all the libraries we use in our application (qt and 3rd party) and by mistake i had statically built the qtftp library.
This seems that had created some "conflicts" that were the cause of the mentioned problem. -
It seems (again!) that the problem indeed wasn't the qt5ftp library but the way i built it.
You see we use dynamic linking for all the libraries we use in our application (qt and 3rd party) and by mistake i had statically built the qtftp library.
This seems that had created some "conflicts" that were the cause of the mentioned problem.@Deathcomes
Hi
Does qt5ftp have any GUI also ?
So we could get a name clash or something? -
@Deathcomes
Hi
Does qt5ftp have any GUI also ?
So we could get a name clash or something?@mrjj said in No matching signals for all controls:
Does qt5ftp have any GUI also ?
No as far as i know.
-
@mrjj said in No matching signals for all controls:
Does qt5ftp have any GUI also ?
No as far as i know.
@Deathcomes
Ok. just wondering how it can make auto connect fail. :)
