error from moc: 'x' does not name a type

[django.Reinhard]

Hi,

I have over 10 plugins and all but one work fine and I run out of ideas how to narrow the bug.

I checked virtual functions, destructor and signals ...
even used interfaces are used by other plugins that work.

Is there a way to make moc more verbose?
That error message is not really helpful.

I checked Qt-guides for plugins too, but did not find any obvious musthave that I might have missed ...

[Christian Ehrlicher]

I don't see how we should help without a single line of code / minimal reproducible example.

[Pl45m4]

@django-Reinhard

Does it really say "X", or is this just a replacement for one of your classes?
If you google it, you'll find some posts about missing forward declarations, that produce similar errors.

[django.Reinhard]

Hi,

thank you very much for your attention.
Of cause 'X' is just a replacement.

I finally found the error:
I had a name clash between enum and class - so I started using namespaces and name clash is history.