EosADAS: update the project structure
1 unresolved thread
1 unresolved thread
Edited by EXT Przemyslaw Lewandowski
Merge request reports
Activity
Filter activity
assigned to @przemyslaw.lewandowski
Questions:
- I moved
EosADAS/imports/EosADAS
toEosADAS/EosADAS
, is that fine or we should skip the lastEosADAS
as well? - I feel like
backend.Data
is a bit ugly, should we skip thebackend
and have just theData
dir in root? - I added
focus
, otherwise the keys did not work. -
examples/EosADAS/EosADAS.qmlproject
I skipped entirely theQMLFiles/Files/etc
as QDS does not rely on it. I'm not sure how CMake generation works, does it use it? If yes I guess that we can keep it, if not, what's their purpose? I read https://doc.qt.io/archives/QtForMCUs-2.5/qtul-qmlproject-reference.html and for example for image it statesThe ImageFiles node adds the given image assets to the project.
though the entire example works without it (and it relies on images). Sorry, it seems that I'm missing something here.
Overall, as discussed, this MR relies on the existing CMakeLists.txt but ideally it should rely on
Enable CMake generator
- which I can do when the questions are answered so I know that this is more or less what we want to achieve.Edited by EXT Przemyslaw Lewandowski- I moved
requested review from @thhartma
added 1 commit
- 40087d5a - EosADAS: update the project structure and rely on CMake generation for QtCreator export
added 1 commit
- d3e6c353 - EosADAS: update the project structure and rely on CMake generation for QtCreator export
17 18 multilanguageSupport: true 19 primaryLanguage: "en" 20 supportedLanguages: [ "en" ] 21 22 Environment { 23 QT_AUTO_SCREEN_SCALE_FACTOR: "1" 24 QT_ENABLE_HIGHDPI_SCALING: "0" 25 QT_LOGGING_RULES: "qt.qml.connections=false" 26 QT_QUICK_CONTROLS_CONF: "qtquickcontrols2.conf" 27 } 28 29 ShaderTool { 30 args: "-s --glsl \"100 es,120,150\" --hlsl 50 --msl 12" 31 files: [ "UntitledProject3DContent/shaders/*" ] 32 } requested review from @thhartma and removed approval
mentioned in commit b0d97e62
Please register or sign in to reply