Details
-
Suggestion
-
Resolution: Unresolved
-
Not Evaluated
-
None
-
None
Description
Currently, if we import multiple Figma projects, the structure is like this:
./MyProject.qmlproject ./CMakeLists.txt ./MyProjectContent/CMakeLists.txt # <-- Monolithic CMake target that contains ALL content ./MyProjectContent/*.ui.qml ./MyProjectContent/FigmaProj1/*.ui.qml ./MyProjectContent/FigmaProj1/assets/* ./MyProjectContent/FigmaProj2/*.ui.qml ./MyProjectContent/FigmaProj2/assets/*
It would be good to support something like this:
./MyProject.qmlproject ./CMakeLists.txt ./MyProjectContent/CMakeLists.txt ./MyProjectContent/*.ui.qml ./MyProjectContent/FigmaProj1/CMakeLists.txt # <-- Dedicated CMake target for FigmaProj1 ./MyProjectContent/FigmaProj1/*.ui.qml ./MyProjectContent/FigmaProj1/assets/* ./MyProjectContent/FigmaProj2/CMakeLists.txt # <-- Dedicated CMake target for FigmaProj2 ./MyProjectContent/FigmaProj2/*.ui.qml ./MyProjectContent/FigmaProj2/assets/*
Use-case
A customer wants their top-level project to contain multiple C++ targets (libraries or executables), and each target could link to a specific QDS-generated target. For example:
- App1 only links to FigmaProj1
- App2 only links to FigmaProj2
- App3 links to both FigmaProj1 and FigmaProj2
Side note: This multi-target project would not use the auto-generated ./App/main.cpp or ./qds.cmake