It started out as a tech demo. Then people started using it and reported bugs and features request. So support for MSVC was added, and version 1.0 was released. It is relatively low maintenance given that Qt maintain binary compatibility anyway (Qt 6 will be another story).
> not sure what binary compatibility has to do with it ...
Because the meta object generated by the verdigris macro will continue to work with newer version of Qt.
But in Qt6, the binary format will change so some adaptations will be required.
And the only reason I discussed that is because earlier in this thread someone claimed "The project is part tech demo for fun, part shut up the people who complain about moc."
> Because the meta object generated by the verdigris macro will continue to work with newer version of Qt. But in Qt6, the binary format will change so some adaptations will be required.
If it Qt6 retains backwards source code compatibility then verdigris should still keep working I guess. If not then yes verdigris will need to change but in neither of these cases do I see binary compatibility as being relevant - if you compiled something for Qt5 and the binary compatibility breaks to Qt6 then this will affect you regardless of having used verdigris or not no?
