No matching signals for all controls

mrjj

@Deathcomes
Do you still have those 3 Make files in the project folder ?
I think they are the real reason.

J.Hilk

@Deathcomes again a shadow build folder will most likely solve your issues 😉

Deathcomes

@mrjj Yes but they are created after every build. Shouldn't they?

@J-Hilk I really appreciate the solution but i have to avoid it because with shadow build i had other problems (probably they were my fault but i don't have time to solve them to nor i am allowed to)

mrjj

@Deathcomes said in No matching signals for all controls:

Yes but they are created after every build. Shouldn't they?

Yes but i just tested with shadow build off and those files go INTO the build
folder. They should not be in project folder and if they are stale they might give all sort of odd errors if compilers sees them.

J.Hilk

@Deathcomes
in that case, make a 2nd folder and clone your clean repo into that, and use that only for release builds.

out of curiosity, what problems were those?

Deathcomes

@mrjj said in No matching signals for all controls:

Yes but i just tested with shadow build off and those files go INTO the build

!!!!!! REALLY???

@J-Hilk I would have to go back 5 years in my memories to tell you and i don't think i'm capable of (I can't remember what i ate yesterday!! :) )!

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.