1137
Link: @CplusplusQt Embedded: @EMBCpp • No DM without prior permission • Behave friendly • No NSFW • No Spam • No unauthorized Bots • Don't advertise other groups
Welcome to the group, -! :-)
Wanna share your story of how you started with Qt, QML or C++? Maybe some nice feature that made you stick with it.
Rules are set on the description of the group. :)
Totally, it distinguishes real software from paper airplanes
Читать полностью…
Dear friends, thank you for all these useful tips. I was able to do it and I am very happy about it. I definitely couldn't have done it without your help.
Читать полностью…
In the age of generative AI though, does cross platform matter that much anymore?
Читать полностью…
And there is at least one infusion pump that uses Qt, and at least two separate companies making heart surgery tools that use Qt.
Читать полностью…
More than as the UI. They use other modules of Qt as well.
Other Autodesk apps use Qt too - 3DS Max, Fusion (360).
Others:
OBS Studio, Ableton Live, VirtualBox, Google Earth, HP RGX remote desktop, VLC, Tesla's infotainment system, high end Keurig office coffee makers, some Samsung refrigerators, older Ford Sync (2021 or 2022 and earlier), daimler Chrysler vehicles, some 2 wheelers in India and china (Qt for MCUs) (there may be some in Europe and US too, I just don't know for certain)...
Some smart ovens, fryers and other equipment used in fast food and fast casual restaurants
Also try running these from Android build directory path.
./gradlew --version
./gradlew build --refresh-dependencies --stacktrace
Try this:
curl -I https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/8.6.0/gradle-8.6.0.pom
Expected: HTTP 200 or a redirect ending successfully. If this fails, fix network/proxy first.
I got this from Claude:
Qt Creator has full Android support through an Android Kit (configure SDK/NDK/JDK paths under Preferences → Devices → Android, or Edit → Preferences in older versions). Once the kit’s set up, you build, deploy, and debug .apk/.aab files directly from the IDE. Under the hood, androiddeployqt generates an Android project and invokes Gradle to package it.
On Gradle: by default Qt uses the Gradle wrapper (gradlew + gradle-wrapper.properties) that ships in Qt’s Android package templates. The wrapper auto-downloads a specific Gradle version on first build. If you want to use a manually installed Gradle instead — common when you’re offline, behind a corporate proxy/firewall, or need a pinned version — you have a few options:
• Point the wrapper at your local install. Edit gradle-wrapper.properties and set distributionUrl to a file:// path of your downloaded Gradle distribution zip. This is the least invasive route and keeps the wrapper mechanics intact.
• Override the package template. Set ANDROID_PACKAGE_SOURCE_DIR in your .pro/CMakeLists.txt to a custom directory containing your own gradle-wrapper.properties (and build.gradle), so Qt doesn’t overwrite your config on each deploy.
• Run Gradle yourself. Let Qt generate the Android project (androiddeployqt --output ...), then invoke your system Gradle (gradle assembleRelease) outside the wrapper entirely. Useful if you want the IDE for editing/debugging but your own build orchestration.
One gotcha worth flagging: the Android Gradle Plugin (AGP) version that Qt’s template requests must be compatible with both your Gradle version and your JDK. Mismatches here are the usual source of cryptic build failures. If you pin Gradle manually, check Qt’s docs for your specific Qt version to see which AGP/Gradle pairing it expects.
Given you’re already doing Qt cross-compilation work, the ANDROID_PACKAGE_SOURCE_DIR route is probably cleanest — it gives you reproducible, version-controlled control over the Gradle setup without fighting Qt’s regeneration. Want me to sketch out a minimal custom package source dir for that?
Thanks. You want separate reports in the other channels?
Читать полностью…
I started with C++ while learning programming fundamentals, but Qt is what made application development really enjoyable for me. The feature that hooked me was the signal-and-slot system—it made handling events and communication between objects feel much cleaner than what I had used before.
Later, when I discovered QML, I loved how quickly I could build and iterate on user interfaces while keeping the backend logic in C++. The combination of a powerful framework, cross-platform support, and great tooling is what made me stick with Qt.
Welcome to the group, @ostrovskiy_e93! :-)
Wanna share your story of how you started with Qt, QML or C++? Maybe some nice feature that made you stick with it.
Rules are set on the description of the group. :)
definitely worth learning for everyone who may work with ui
Читать полностью…
much more than that,
yes. it's de-facto standard for UI at linux, so it's used in embedded everywhere where you can boot linux distributuve, eg some car ui
cross-platform, popular... no analog
Oh, DaVinci surgical robot uses Qt (more than just the UI components afaik)
Читать полностью…
AGP 8.6.0 needs Gradle 8.7+ and JDK 17. If your Qt kit points to JDK 8/11 or an older Gradle wrapper, you may see this too.
So, it is not a download problem.
Is any of the files: build.gradle or gradle-wrapper.properties edited manually?
My version is 6.8, I don't think it has changed much since the last version you used.
Excuse me, what was your suggestion?