Thanks Alexandru !
I was indeed toying around with QML_FOREIGN to overcome some of those
limits, but, as I reported in a separate mail yesterday, I also encountered
problems, where a "foreign" type from a separate library generated
```Warning: Refusing to generate non-lowercase name "A" for unknown
Hi,
As far as I know this currently doesn't work, and is a variation of the
following bug report:
https://bugreports.qt.io/browse/QTBUG-122702
After a very quick scan, I believe the docs don't mention this limitation.
The happy path for qml modules is to have the library / executable created in
he static library’s plugin to the
> application binary. Hence, the last bit of linking to ‘qmlplugin’. The
> tooling generates this in the build directory and it contains the necessary
> code to register the QML types and load the static library.
>
>
>
> Hope that helps
, August 14, 2024 at 08:29
To: interestqt-project.org
Subject: [Interest] creating QML module in a subdirectory of backing target
hello,
in a large CMake / Qt project of mine, I'm building a (shared) library in some
directory `A`.
Now I want to add a QML module for that, but due to various constr
hello,
in a large CMake / Qt project of mine, I'm building a (shared) library in
some directory `A`.
Now I want to add a QML module for that, but due to various constraints
want to do that in a subdirectory `A/qml`.
That is, I have
A/
├── CMakeLists.txt
├── qml
│ ├── CMakeLists.txt
where `A/CM
