Moc not generating functions

[Christian Ehrlicher]

@Redman said in Moc not generating functions:

SOURCES +=
$$files("$$PWD/*.cpp",true) \

Apart from the really strange way to add sources - this does not add configuration.cpp.

As you can see in the linker error not the moc stuff is missing but the functions defined in configuration.cpp

[Redman]

@Christian-Ehrlicher
Any tips on how to add sources without typing every file specifically. I assumed as long as the files showed up in the project tree building them is no problem. Which was true until now.

[Christian Ehrlicher]

@Redman Type all. But that's not the problem here.

[Redman]

@Christian-Ehrlicher So how can I tell moc to add the functions?

[Christian Ehrlicher]

@Redman said in Moc not generating functions:

@Christian-Ehrlicher So how can I tell moc to add the functions?

As I already said there is no problem with moc but you don't compile configuration.cpp anywhere.

[Redman]

@Christian-Ehrlicher
The service.exe, which is configured in app.pro, is built correct. The exe can only be a result of a successful compilation. So I'd assume configuration.cpp is compiled

[Christian Ehrlicher]

@Redman said in Moc not generating functions:

So I'd assume configuration.cpp is compiled

Don't assume, check.
You did not show any pro file where you compile configuration.cpp so my answer still stands...

[Redman]

@Christian-Ehrlicher

I think this should answer your question.

To elaborate further:
project.pro

  SUBDIRS = \
            client \
            logger \
            service
			
  # where to find the sub projects - give the folders
  client.subdir = src/client
  logger.subdir  = src/logger
  service.subdir  = src/service

service.pro

TEMPLATE = subdirs

SUBDIRS = \
        app \
        test \

# where to find the sub projects - give the folders
app.subdir = app
test.subdir  = test

test.depends = app

So far all I had to do was include the sources and headers in the pro files and the projects simply compiled. Please enlighten me if I'm missing something crucial.

update:
After dumpbin.exe Configuration.obj /disasm

Even though we see the function is present in the obj file I still get following error

error: LNK2019: unresolved external symbol ""public: __cdecl Configuration::Configuration(class QObject *)" (??0Configuration@@QEAA@PEAVQObject@@@Z)" in function ""private: static void __cdecl TestConfig::qt_static_metacall(class QObject *,enum QMetaObject::Call,int,void * *)" (?qt_static_metacall@TestConfig@@CAXPEAVQObject@@W4Call@QMetaObject@@HPEAPEAX@Z)".

What makes me wonder is the second part of the error message. But I guess thats just how Qt invokes all function calls for classes that inherit from QObject.

[Christian Ehrlicher]

Provide a minimal, compilable example. Don't use global globs to add files so we can see where exactly configuration.cpp is compiled into since you still (after 5 posts from me) failed to do so.

[Redman]

@Christian-Ehrlicher Here you go
https://file.io/dO55Ata0j6rm
https://easyupload.io/bwbtos

[Christian Ehrlicher]

As I said - there is no library where you link your configuration.cpp - you only compile it directly to your app.
So either also directly link it to your testcase or create a library and link the library to your app and your test.

[SimonSchroeder]

@Redman said in Moc not generating functions:

SOURCES +=
$$files("$$PWD/src/*.cpp", true)

If you insist on using this any further, you need to adjust your paths. To add configuration.cpp to your test.pro the path needs to be $$PWD/../app/src/*.cpp because $$PWD is service/test, but your sources are locate in service/app/src. $$PWD stands for "print working directory" and thus your working directory for app.pro and test.pro is different.

[Redman]

Solution was to create SUBDIR .pro with lib and test subdirs. In lib I build a .dll from app and include the dll in test