HI,
While I am trying to get dockers running with QtCreator 17, I found the
following issues which I would like to discuss here before creating
them in the issue tracker. Which of them are still relevant in QtC 18?
1. You can select different docker devices for build and run. But the debugger
is always taken from the build docker. One cannot even select
a debugger from the run device manually. This is a blocker as the build device
cannot run the application (that's the reason why you have a
separate run device and docker image).
2. The default name of the kit is %{Device:Name}. The Device:Name is taken from
the Run device which surprises me because the build device
is surely more important, isn't it?
3. Qt Version, Compilers and Debuggers are all named after the docker image
name, tag, id and some extra text. At least in my case the
docker image names are build from the docker registry (some artifactory name),
some folders to structure the dockers and the tag (which is
pretty long as it lists several component versions used in the image). At the
end the strings are something like 160 characters long which
is an issue in the UI.
4. Detected debuggers are never removed automatically and cannot be removed
manually. While Qt versions and compilers are removed
automatically when the device is deleted, the detected debuggers stay and the
list grows longer and longer over time.
All in all there are far too many steps needed to get a clean device and kit
set up to build and run and application using docker. The new
concept with the json description in QtC 18 seems like a good way to go. Does
this solve some of the issues (like the naming or selection of
the debugger)?
Regards, Jochen
--
Qt-creator mailing list
[email protected]
https://lists.qt-project.org/listinfo/qt-creator
