# Qt6 tracking thread

**URL:** <https://discuss.avogadro.cc/t/qt6-tracking-thread/5592>\
**Category:** Development\
**Created:** [September 16, 2024, 8:21pm UTC](https://discuss.avogadro.cc/t/qt6-tracking-thread/5592 "2024-09-16T20:21:53Z")\
**Posts on this page:** 1\
**Showing post:** 4

<div class="post-metadata">

**Author:** ![matterhorn103](https://discuss.avogadro.cc/user_avatar/discuss.avogadro.cc/matterhorn103/32/1751_2.png) [@matterhorn103](https://discuss.avogadro.cc/u/matterhorn103)\
**Post date:** [September 16, 2024, 8:53pm UTC](https://discuss.avogadro.cc/t/qt6-tracking-thread/5592/4 "2024-09-16T20:53:08Z")

</div>

> [@ghutchis](#):
>
> The main pain point is moving to the new Qt6 deployment mechanism, but it’s a solvable problem.

Is that something I can look at and put time into helping with?

You’ve mentioned the deployment thing [before](https://discuss.avogadro.cc/t/avogadro-1-97-0-doesnt-run-on-windows-11-arm/4018/9), but I’ve never really understood what the deploy script _is_, what it does that the CMake files + the GitHub actions don’t already do, and where the current script can be found in the repo.

---

_[View the full topic](https://discuss.avogadro.cc/t/qt6-tracking-thread/5592)._