lifemaps/qt6-migration-pipeline
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Adds migration for lts/projects and lts/application (tbc)

Browse Source 
Entire-Checkpoint: 01M3BV674BDGYRJJJCMHP5ZBCF
This commit is contained in:
torsten committed 2026-09-25 08:33:54 +00:00
1 parent 5f59c0e5df
commit ea90652fd4
2 files changed
+386 -9
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

prompts/migrate-lts-tools-d-and-l.md
+9 -9
View File
@@ -94,15 +94,15 @@ Work in the Qt6 target tree only. Do not modify the Qt5 legacy tree.
## Scope rules
Touch files outside the targets directories only when directly required to configure, generate, build, link, test, or validate these services.
Touch files outside the targets directories only when directly required to configure, generate, build, link, test, or validate these targets.
Allowed outside-scope changes:
- parent CMakeLists.txt entries for these services
- central CMake helper fixes required by these services
- shared include path fixes required by these services
- RTI, codegen, ndsgen, KTextTemplate, or Grantlee integration fixes required by these services
- test infrastructure needed by tests for these services
- parent CMakeLists.txt entries for these targets
- central CMake helper fixes required by these targets
- shared include path fixes required by these targets
- RTI, codegen, ndsgen, KTextTemplate, or Grantlee integration fixes required by these targets
- test infrastructure needed by tests for these targets
- new_docker_build.sh changes needed to run those tests
- minimal Jenkins CI discovery or policy updates needed for those tests
- relocation of required stubs or forward declarations to allowed directories
@@ -196,7 +196,7 @@ For each cmake target, inspect and migrate only as needed:
- CMakeLists.txt and parent CMake registration
- ui, qrc, resource, plugin, and service metadata
- RTI IDL, ndsgen, KTextTemplate, and Grantlee inputs/templates
- tests directly tied to these services
- tests directly tied to these targets
Fix only real Qt6/C++17 build issues, such as:
@@ -306,7 +306,7 @@ Jenkins CI must be able to discover and run the new tests, or verify that new_do
## Required procedure
1. Inspect repository state, branch, working tree, submodules, required prompts, service paths, and forward-declaration directories.
2. Compare Qt5 source services with Qt6 targets. Classify files as already migrated, missing, stale, generated, intentionally removed, build-only, or needing Qt6 adaptation.
2. Compare Qt5 source targets with Qt6 targets. Classify files as already migrated, missing, stale, generated, intentionally removed, build-only, or needing Qt6 adaptation.
3. Identify dependencies, generated inputs, Qt modules, parent CMake entries, removed-module references, LogViewer interactions, and required stub/forward-declaration relocations.
4. Apply the smallest valid migration changes.
5. Add required CTest tests for C++ changes.
@@ -358,7 +358,7 @@ Success requires:
- configure, build, and CTest pass with BUILD_RTI=ON and BUILD_GRANTLEE=ON and BUILD_ARCGIS=ON
- new_docker_build.sh runs the relevant tests and fails on test failure
- Jenkins/policy discovery accepts the new tests and validation changes
- no active Qt5 imported target links remain for these services
- no active Qt5 imported target links remain for these targets
- generated outputs are build-tree only and freshly produced when required
- no generated outputs are committed or consumed from the source tree
- no fake generated files, dummy files, mocks, placeholders, or stubbed generated outputs exist