No matching signals for all controls
-
@mrjj Shouldn't Windows updates affect my other projects?
My project folder is as follows:
debug(folder) release(folder) ... my .h and .cpp files ... Makefile Makefile.Debug Makefile.Release Project.pro Project.pro.user ui_mainwindow.h@Deathcomes go into your project settings turn on shadow build folder, if it's already checked, what I highly doubt from your folder structure, change the target folder name. Add a 0 or something
-
@Deathcomes said in No matching signals for all controls:
Makefile
Makefile.Debug
Makefile.ReleaseThose seems in wrong place. should be in the build folder.
-
@Deathcomes go into your project settings turn on shadow build folder, if it's already checked, what I highly doubt from your folder structure, change the target folder name. Add a 0 or something
@J-Hilk I have never used shadow build! I had other problems before and i have avoided it. Thanks for the suggestion though!
@mrjj In all my projects these files are on the same spot (and the other projects work).
Thanks a lot for your help but i solved it (although i don't know how!!). I did a "checkout" again (after i deleted the folder contents) and re-configured/re-build the project and it worked. There is a slight chance (but i'm not sure), that the first time i did the checkout i immediately built the project, without removing the shadow build. Then i removed it and (probably?) that created this "bad state"!
Sorry if this sound silly but i'm not versed on the "internals" of Qt!
Also sorry, and thanks for not growling, if i did some mistakes with my English! -
@J-Hilk I have never used shadow build! I had other problems before and i have avoided it. Thanks for the suggestion though!
@mrjj In all my projects these files are on the same spot (and the other projects work).
Thanks a lot for your help but i solved it (although i don't know how!!). I did a "checkout" again (after i deleted the folder contents) and re-configured/re-build the project and it worked. There is a slight chance (but i'm not sure), that the first time i did the checkout i immediately built the project, without removing the shadow build. Then i removed it and (probably?) that created this "bad state"!
Sorry if this sound silly but i'm not versed on the "internals" of Qt!
Also sorry, and thanks for not growling, if i did some mistakes with my English!@Deathcomes
Hi
Ok, its a bit odd with those files as I never had any in the project folder.
But I always use the shadow folder to build on ram disk so maybe why.But you are right. Shadow build can mess up the build. I tried it once with an
external lib. But that was like 1 in 1000 :)In any case, good you found out and your English is more than good enough.
Please flag the post as solved using the Topic Tool button on the first post.
-
I'm returning with some more info on the problem (yes i know i said it resolved itself but i was horribly wrong!).
The problem only occurs when i build/run in Debug configuration(not sure if it is really named "configuration")!
-
I'm returning with some more info on the problem (yes i know i said it resolved itself but i was horribly wrong!).
The problem only occurs when i build/run in Debug configuration(not sure if it is really named "configuration")!
@Deathcomes
Do you still have those 3 Make files in the project folder ?
I think they are the real reason. -
I'm returning with some more info on the problem (yes i know i said it resolved itself but i was horribly wrong!).
The problem only occurs when i build/run in Debug configuration(not sure if it is really named "configuration")!
@Deathcomes again a shadow build folder will most likely solve your issues 😉
-
@Deathcomes
Do you still have those 3 Make files in the project folder ?
I think they are the real reason.@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)
-
@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. -
@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)
@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 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.@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!! :) )!
-
@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 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
no. you are right.
Tested with a new project and disabled shadow
then they come in the folder
I just been using shadows build since day one so never noticed.
-
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. -
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.@mrjj Ok i will try.
-
@mrjj Unfortunately! Same problem.
@Deathcomes
and that was without re-using the .pro file ?
That is very, very odd. -
@Deathcomes
and that was without re-using the .pro file ?
That is very, very odd.@mrjj Yes the only thing i "used" from the old pro was this
from this (default when creating a project)
QT += core guito this
QT += core gui winextras sql network concurrentand 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 Yes the only thing i "used" from the old pro was this
from this (default when creating a project)
QT += core guito this
QT += core gui winextras sql network concurrentand also i added this because i was missing some libraries
LIBS += -LC:/Qt/Qt5.2.1/5.2.1/mingw48_32/lib -lQt5Ftp -lKernel32@Deathcomes
Ok that seems fine.does the connect work if you use
the connect statement ?
