Generated output file names

[ahayzen-kdab]

Options for the file name

• Use the name of the QObject
  • Prevents multiple QObjects per macro block
• Use the name of the module (with attribute override?)
  • Potentially the simplest for now
  • Can have collisions if you have module_a::ffi and module_b::ffi as your modules
  • Could have an attribute to pick a custom one eg #[cxx_qt::bridge(file_stem="my_object")]
  • Only prevents us combining two macro blocks from the same file like CXX does (although their support does seem to have issues as well)
• Use the name of the input file
  • This is what CXX is able to do, we can do it with nightly API WIP: cxx-qt-build: use filename for rust name  #200 Tracking issue for proc_macro::Span inspection APIs rust-lang/rust#54725
  • CXX is able to do this easily as they don't need to put the include line into the macro generated code only the C++ side
  • Whereas we need to be able to tell the filename from the macro

Where is this used

• In the developers C++ code to include the C++ header (eg #include "cxx-qt-gen/include/my_object.cxxqt.h)
• In the Rust macro expansion we need to have include!("my_object.cxxqt.h")
• In the generated C++ code it's used for including the CXX header (eg #include "cxx-qt-gen/include/my_object.cxx.h) and from the cpp file to include the header file

[ahayzen-kdab]

Potentially use the build script to inject the file_stem into the cxxqt::bridge as an attribute.

[ahayzen-kdab]

We can't as the build.rs doesn't change the Rust source

[ahayzen-kdab]

For now use the module name + option to choose a custom with the macro attribute. Then if the nightly API becomes stable transfer to that.