Manage QtC Plugins
Qt Creator has many Plugins installed as default.
Open the list of Qt Creator Plugins:
It’s a good idea to disable Plugins you’re not using.
per ex. I manage all my Git repos using GitTower and I don’t want always to be asked about my source repo.
Open the list of Qt Creator Plugins – then uncheck all unwanted Version Controls.
Do the same with the needed Device Support – I only need Android and iOS
Restart Qt Creator.
GoTo Preferences – Kits and verify that the default Kit is recognized:
Environment – External Tools – Linguist
I’m developing business apps and business apps always need support of languages (i18n). Configuring the External Tools for Linguist (Qt’s Tool to translate text from your QML and C++ sources) will make it more comfortable.
As first step we’ll add the Linguist App.You’ll find the Linguist at 5.15.13 –> clang_64 –> bin:
Under Preferences –> Environment –> External Tools there already exist access to commands for lupdate and lrelease. (lupdate is looking for the strings you marked as translatable and to create or update the translation files <app>.ts. Using Linguist or external tools you can then translate the strings. lrelease compiles these translations from *.ts into *.qm. Only *.qml files will be deployed to your device)
I found out that the default configuration doesn’t work if Android or iOS Kit is selected – so I’m using the executable from …/5.15.13/clang_64/bin.
Hint: Have not tested if those problems still exist in 5.15.13, but spend no time on this because soon I have to switch to Camake
and the same for lrelease:
It’s a good idea to test if the External command works and opens Linguist from inside QtCreator.
it’s a good idea to use a shortcut:
Build & Run
Set your Projects Directory for 5.15.13, if you aren’t using default directories as I’m doing.
Hint: Try to avoid Spaces in your directory name / path
Application Output: It makes sense to ‘Merge sterr and stdout. You can also decide when output panes will be automatically opened for debug and run
Compile Output: if you want – you can automatically open the Pane when building:
Build and Run – Shadow Builds
Building for Debug or Release will create a (shadow) Build Directory. From the name of the build dir you can recognize for which platform (Desktop, Android, iOS) this build is, which Qt Version used and see if it’s a Debug or Release build.
Hint: If something wrong with your project, it’s a good idea to delete the shadow build dir and build again.
I always slightly modify the Default build directory:
In this example builds were done with Qt 5.15.12:
Inside android-build you’ll find the APK / aab, inside iOS-build you see the generated Xcode project and can open from here.
You must be logged in to post a comment.