No matching signals for all controls

Deathcomes

@mrjj Also i just tried it with another project (build/run in debug mode without debugger) and the signal slots connected properly AND the "Makefile" files have been created inside the root folder of the project.
Could it be something wrong with my configuration?

mrjj

@Deathcomes
no. you are right.
Tested with a new project and disabled shadow
then they come in the folder
alt text

I just been using shadows build since day one so never noticed.

mrjj

Hi

Could it be something wrong with my configuration?

well, other projects works so thats no so likely.
but i wonder if something up with that .pro file.

You could try recreate the project in a new folder.
copy all .h and .cpp and then add to Project file using "Add existing " when right clicking on the project top name.

Deathcomes

@mrjj Ok i will try.

Deathcomes

@mrjj Unfortunately! Same problem.

mrjj

@Deathcomes
and that was without re-using the .pro file ?
That is very, very odd.

Deathcomes

@mrjj Yes the only thing i "used" from the old pro was this

from this (default when creating a project)

QT       += core gui

to this

QT       += core gui winextras sql network concurrent

and also i added this because i was missing some libraries

LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32

mrjj

@Deathcomes
Ok that seems fine.

does the connect work if you use
the connect statement ?

Deathcomes

@mrjj Yes because i have other connect with custom slots

mrjj

@Deathcomes
so its only the auto matching that complains ?

Deathcomes

@mrjj Correct

mrjj

@Deathcomes
I have no idea why then it must not seem then when running
QMetaObject::connectSlotsByName(Widget);

Deathcomes

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 -lKernel32

which 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.

mrjj

@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

@mrjj said in No matching signals for all controls:

Maybe it screws up the meta data somehow.

How can i check it?

mrjj

@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#3539

maybe we could dump the names it sees with and without ftp lib.

JonB

@Deathcomes
One question: why is something as old as Qt 5.2 involved in your build?

Deathcomes

@JonB We started development on that version and there was never a necessity to upgrade to a newer version.

Deathcomes

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.

mrjj

@Deathcomes
Hi
Does qt5ftp have any GUI also ?
So we could get a name clash or something?