On Wed, Oct 01, 2025 at 04:21:42PM +0200, Jochen Becher via Qt-creator wrote: > Hi, > > I set up a development docker with Qt 6.8.3, gcc, qbs, cmake, clangd, ssh and > use it with QtCreator 18 beta1. It works quite fine but when I try clang-tidy > it fails because it uses clang-tidy on the host system, not in the docker. > Are you aware of this weakness
A few people are. > and is it planned to fix this until release of QtC 18? So far it wasn't. 18 is already in feature freeze and very soon in string/UI freeze. But now I'll have a look next week. Maybe the clang-tidy case can still be done and sneaked into the release. > I've got the impression that support of development docker will be a > focus in QtC 18. Kind of, but actually not as "docker", but "anything *nix-ish with ssh access", which in practice should cover quite a few of the docker cases. However, to make "everything" work in this setup is a bit of effort as all code that accesses files or executes processes need to be adjusted. I also think it was never officially mentioned let alone promised to be complete at 18 release time. > What about support for the other analysis tools like CPU usage, QML Profiler > and valgrind? Are those support on development dockers? My personal plan is to have "reasonable 'remote' setups" being handled "the same" as a local setup, i.e. ideally it should not matter where sources are located, where stuff is built and where it is run or debugged or profiled, as long as the relevant "devices" can communicated with each oteher. Of cource there are practical limitations stemming e.g, from latencies for truly remote setups, but specifically for docker containers on the same machine on which Creator itself runs I believe we can get pretty far. Regards. Andre' -- Qt-creator mailing list [email protected] https://lists.qt-project.org/listinfo/qt-creator
