Andrew Hayzen
Andrew Hayzen
Note that the path of mod's can be influenced by an attribute https://doc.rust-lang.org/reference/items/modules.html#the-path-attribute We will need to track the full mod path somehow.
Also note that this will need to affect the C++ namespace and file generation too, and the include paths will need updating.
To avoid collisions in QML we may need to allow for a custom name to be specified in the macro, eg `#[cxx_qt(QObject, qml_name = "MyObject")]`
So i found out you can use docker/podman in github action machines, i need to see how many permissions there are available as then there is a potentially simple way...
Note that using `std::int32_t` confused QML in Qt 5 but not Qt 6 .. https://github.com/ahayzen-kdab/cxx-qt/tree/use-std-integer-types
With the new API this is now irrelevant as we are a CXX module.
This needs more thought around how it can figure out the names, probably will be combined with the generator phase refactor. As it needs to know how the case conversion...
I assume you mean multiple crates ? And not multiple modules, as we support already defining multiple modules that are in the same crate and are then expose multiple QObject's...
So this goes against the current goals and focus of this tool, of not exposing intimate details about Qt to Rust and limiting scope to only plugins and modules which...
Note that this is related to #53