undefined reference to `vtable for

[JonB]

@SPlatten
OK for the definition! [I'm about to post a question in the C++ Gurus sub-forum about this :) ]

the message is just name space and class name

But are we to assume that is the (correct) namespace & class name specifically for staledata_t?

I think between you, you have solved the issue

However, that appears to not be all, the same message is still reported.

Are these two statements meant to be consistent?

[SPlatten]

This post is deleted!

[J.Hilk]

@SPlatten said in undefined reference to `vtable for:

const QString ip() { return m_ip; }

btw, the const here has no meaning. I think you meant to write:

 QString ip() const { return m_ip; }

or

const QString &ip() { return m_ip; }

or

const QString &ip() const { return m_ip; }

;-)

[SPlatten]

This post is deleted!

[JoeCFD]

In this case, often you need to make clean and rebuild your project.
in cmake: remove build fold completely. rebuild everything
in qmake: make distclean. then rebuild.

[JoeCFD]

This post is deleted!

[J.Hilk]

@SPlatten sooo, what exactly is at line 47 ?

[SPlatten]

This post is deleted!

[SPlatten]

This post is deleted!

[JonB]

@SPlatten
To be clear: you mean that the file you have been showing us is the config.H file of the error message? And the implementation file is config.cpp which is compiled to config.o. And the line #47

staledata_t() : QObject(nullptr)

is the one just under the public: you show earlier?

[SPlatten]

This post is deleted!

[SPlatten]

This post is deleted!

[JonB]

@SPlatten
Dunno at this point, a bit difficult to spot with all that's going on. For me I would do the usual: comment "everything" out, preferably including the namespaces, till you get rid of that message. Then add back in....

[J.Hilk]

@SPlatten your class compiles perfectly fine for me, at least as long as I add the implementation of m_nextUDN, where exactly do you do that ?

I know you said/showed, you do it, but where exactly?

[SPlatten]

This post is deleted!

[JoeCFD]

Often make clean is not enough especially when cmake is used. Remove the whole build dir and recreate it.

[JonB]

@SPlatten
Yeah, but is that "global scope", i.e. not inside anything else?

@J-Hilk
The trouble is, without m_nextUDN defined properly, I do not get

undefined reference to vtable for asv::scm::helm::staledata_t'

message, I get complaint about m_nextUDN not being defined....

[mchinand]

Do the capital C/H extensions force compiling this with the c compiler instead of c++?

[J.Hilk]

@JonB yes, the error message probably changed after @SPlatten added the missing function body that the Q_PROPERTY macro referred to.

@SPlatten are you sure config.c is party of your project ? :D so the linker can find it

[JonB]

@SPlatten
I'm with @JoeCFD on one thing: if you get "incomprehensible"/"impossible" error messages, especially about vtables, with Qt you (may) need to do a "change underpants"-type clean rebuild. Preferable buy a new machine ;-) But if not delete the whole build output directory and try again.....