Optional: Try another platform

Run the completed Session counter with another toolkit while keeping its Rust code, translations, and walkthrough. Qt runs on the same Mac as the AppKit lessons, so you can compare the controls before setting up another operating system.

Run with Qt on your Mac

Install Qt 6 and pkg-config using the macOS setup instructions. With Homebrew:

brew install qt pkg-config

Add this line to the existing [features] table in your app’s Cargo.toml. Keep the existing mock and appkit entries:

qt = ["day/qt"]

From the app directory, create the target files and check the tools:

day project add-target macos-qt
day doctor --toolkit qt
day launch -t macos-qt

The window shows the same counter using Qt controls. Add two sessions, open the summary, return, and reset the count. Quit, then run the same automated walkthrough against this target:

day launch -t macos-qt --locale en --script dayscript/session-counter.yaml

A successful walkthrough exits with code 0. Check the layout at the minimum window size and try keyboard navigation as well. macos-qt is a development target; the supported Qt deployment target is Linux. See platform support.

Choose another operating system

Each target needs its matching Cargo feature, host tools, and platform configuration. Follow its setup page before adding it with day project add-target <target>.

TargetCargo featureSetup
ios-uikituikit = ["day/uikit"]iOS
android-mdcandroid = ["day/android"]Android
linux-gtkgtk = ["day/gtk"]Linux GTK
linux-qtqt = ["day/qt"]Linux Qt
windows-winuiwinui = ["day/winui"]Windows
harmony-arkuiarkui = ["day/arkui"]HarmonyOS, experimental
web-domdom = ["day/dom"]Browser, experimental

Troubleshooting

If Cargo reports that the app has no qt feature, confirm the new entry is inside [features]. If doctor cannot find Qt, check that pkg-config can locate the installed Qt libraries. Enable only one toolkit per binary; day launch -t selects the matching backend feature for you.

Return to the complete app or choose a task guide.