[GH-ISSUE #119] Auto generating interop C++/C# code. #71

New issue

Open

opened 2026-05-05 11:03:25 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 11:03:25 -06:00

Owner

Originally created by @pauldotknopf on GitHub (Apr 14, 2019).
Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/119

Right now, it is cumbersome to flesh out the boilerplate needed for some simple getters/setters.

I'd like to have another console project where we can define the interop API with C# models, and then generate the C++/C# to go back and forth.

SWIG does someting similar, but I'd prefer a home-grown approach that uses QSharedPointer and special Qt meta-system support.

Originally created by @pauldotknopf on GitHub (Apr 14, 2019). Original GitHub issue: https://github.com/qmlnet/qmlnet/issues/119 Right now, it is cumbersome to flesh out the boilerplate needed for some simple getters/setters. I'd like to have another console project where we can define the interop API with C# models, and then generate the C++/C# to go back and forth. SWIG does someting similar, but I'd prefer a home-grown approach that uses ```QSharedPointer``` and special Qt meta-system support.

gitea-mirror commented

2026-05-05 11:03:27 -06:00

Author

Owner

@pauldotknopf commented on GitHub (Jul 18, 2019):

Note, this is for the internal interop only, not the classes defined in your implementation.

@pauldotknopf commented on GitHub (Jul 18, 2019): Note, this is for the internal interop only, not the classes defined in your implementation.

gitea-mirror commented

2026-05-05 11:03:28 -06:00

Author

Owner

@vadi2 commented on GitHub (Jul 18, 2019):

Would this mean that any Qt class would be available for use, instead of only ones marked as Q_INVOKABLE right now?

@vadi2 commented on GitHub (Jul 18, 2019): Would this mean that any Qt class would be available for use, instead of only ones marked as `Q_INVOKABLE` right now?

gitea-mirror commented

2026-05-05 11:03:29 -06:00

Author

Owner

@pauldotknopf commented on GitHub (Jul 18, 2019):

No, unfortunately. The properties/methods that are dynamically invokable must be made visible to the meta object system. This is only done via Q_PROPERTY and Q_INVOKABLE (or slots).

@pauldotknopf commented on GitHub (Jul 18, 2019): No, unfortunately. The properties/methods that are dynamically invokable must be made visible to the meta object system. This is only done via Q_PROPERTY and Q_INVOKABLE (or slots).