A Gradle plugin for generating QRC File for QML Projects.
This project is licensed under the terms of the MIT license.
1 . Apply the plugin:
plugins {
id 'all.shared.gradle.qrc-file-generator' version '1.0.0'
}2 . Add the following line to the QT/QML project .pro file:
- This will point the QML Project build to the right spot, i.e. pointing to the QRC's Generated File.
RESOURCES += 'src/main/resources/qml.qrc'3 . Execute generateQrcFile task.
- This will generate qrc file based on default values:
- inputs will be all the
.qml,.js,.mjs,.conf,.png,.jpgand.ttffiles located in foldersrc/main/resources. - output will be generated in
src/main/resourcesfolder, with nameqml.qrc.
- inputs will be all the
4 . Jump to Using/Configuration, for customization or digging on How it works.
The automatic generation of the .qrc file required when working with QML. It is frequent to miss to update the .qrc file, when for example add a new file, changing a file name, changing a file location, etc. This plugin will allow to never worry about that.
- Offers a unique task,
generateQrcFile, which automatically generates the required.qrcfile based on default values. - Allows for customization of input and output values.
- Applies the required plugins to the project:
- None
- Apply the plugin:
plugins {
id 'all.shared.gradle.qrc-file-generator' version '1.0.0'
}The following options are available for customization:
sourceExtensions: string[]: sets extensions to look for, that define the QML resources.- default:
['qml', 'js', 'mjs', 'conf', 'png', 'jpg', 'ttf'] - These are internally processed using File lister plugin.
- default:
sourceFolder: string: specifies the path, relative to the root of the project, to look forsourceExtensionsfiles.- default:
'src/main/resources' - should not end with
/.
- default:
destinationFile: string: specifies the file name.- default:
'qml.qrc'
- default:
destinationFolder: string: sets the path, relative to the root of the project, wheredestinationFilewill be created.- default:
'src/main/resources' - included resource files must be located in same folder where
.qrcfile is located or a subfolder (RCC requirement). - should not end with
/.
- default:
excludes: string[]: specifies ANT patterns for exclusions.- default:
[] - These are internally processed using File lister plugin.
- default:
rccVersion: string: sets RCC version.- default:
'1.0'
- default:
rccPrefix: string: sets RCC prefix.- default:
'/'
- default:
Basically generateQrcFile task will look for resources based on sourceExtensions in sourceFolder and subfolders, excluding any pattern set in excludes, and then will create destinationFile in the destinationFolder with rccVersion and rccPrefix.
- Resulting paths inside
destinationFilewill be relative to the directory containing thedestinationFilefile.
E.g.:
Given the following folder structure, and using default values:
src/
main/
cpp/
main.cpp
resources/
main.qml
folderA/
someComponent.qml
someIcon.png
folderB/
otherComponent.qml
folderB1/
some.mjs
fonts/
fontA.ttf
will generate the xml file, src/main/resources/qml.qrc:
<!DOCTYPE RCC>
<RCC version="1.0">
<qresource prefix="/">
<file>main.qml</file>
<file>folderA/someComponent.qml</file>
<file>folderA/someIcon.png</file>
<file>folderB/otherComponent.qml</file>
<file>folderB/folderB1/some.mjs</file>
<file>fonts/fontA.ttf</file>
</qresource>
</RCC>Customization can be done using plugin options:
qrcFileGenerator {
sourceFolder = ..
sourceExtensions = ..
destinationFile = ..
destinationFolder = ..
excludes = ..
rccVersion = ..
rccPrefix = ..
}Customization can be done using task options:
generateQrcFile {
sourceFolder = ..
sourceExtensions = ..
destinationFile = ..
destinationFolder = ..
excludes = ..
rccVersion = ..
rccPrefix = ..
}E.G.:
Setting new Extensions:
qrcFileGenerator {
sourceExtensions = ['qml', 'js', 'svg']
}Adding Extensions:
qrcFileGenerator {
sourceExtensions += 'svg'
}Finally, It's useful to set a dependency on generateQrcFile for the task that calls the qmake command, e.g.:
someQmakeTask {
dependsOn 'generateQrcFile'
}- It is not necessary to include qml.qrc file in the control version repository, so can be added to the
.gitignorefile:
qml.qrcClone or download the project[1], in the desired folder execute:
git clone https://github.com/gmullerb/qrc-file-generator- No need, only download and run (It's Gradle! Yes!).
- Remove the Git Origin:
git remote remove origin. - Add your Git origin:
git remote add origin https://gitlab.com/yourUser/yourRepo.git. - Remove the License for 'All rights reserved' projects, or Modify the License for your needs.
- Change the
all.shared.gradle.qrc-file-generator.propertiesfile name to your plugin Id, e.g.some.pluginId.properties.
-
To build it:
gradlew: this will run default task, orgradlew build.
-
To assess files:
gradlew assessCommon: will check common style of files.gradlew assessGradle: will check code style of Gradle's.gradlew codenarcMain: will check code style of Groovy's source files.gradlew codenarcTest: will check code style of Groovy's test files.assembletask depends on these four tasks.
-
To test code:
gradlew test- This will run jacoco code coverage [1].
-
To publish plugin:
./gradlew -PPLUGIN_ID=some.pluginId publishPlugins-PPLUGIN_IDindicates the plugin id.
-
To get all the tasks for the project:
gradlew tasks --all
| [1] May not get 100% since Groovy adds some extra code, that may not be tested.
/src
/main
/groovy
/test
/groovy
src/main/groovy: Source code files.QrcFileGeneratoris where all the plugin's magic happens.QrcBodyGeneratoris where all the generation's magic happens.
src/test/groovy: Test code files[1].
[1] Tests are done using JUnit, Mockito and Spy Project Factory.
All all.shared.gradle plugins define:
- PluginNamePlugin: which contains the class implements
Plugininterface. - PluginNameExtension: which represent the extension of the plugin.
- If Tasks are define, then their names will be TaskNameTask.
- If Actions are define, then their names will be ActionNameAction.
All all.shared.gradle plugins have two static members:
-
String EXTENSION_NAME: This will have the name of the extension that the plugin add.- if the plugin does not add an extension the this field will not exist.
-
String TASK_NAME: This will have the name of the unique task that the plugin add.- if the plugin does not add a task or add more than one task, then this field will not exist.
-
boolean complement(final ..): will apply the plugin and return true if successful, false otherwise.- this methods is exactly equivalent to the instance
applymethod, but without instantiate the class if not required.
- this methods is exactly equivalent to the instance
Both may be useful when applying the plugin when creating custom plugins.
All all.shared.gradle plugins "silently" fail when the extension can not be added.
CHANGELOG.md: add information of notable changes for each version here, chronologically ordered [1].
[1] Keep a Changelog
- Use code style verification tools => Encourages Best Practices, Efficiency, Readability and Learnability.
- Start testing early => Encourages Reliability and Maintainability.
- Code Review everything => Encourages Functional suitability, Performance Efficiency and Teamwork.
Don't forget:
- Love what you do.
- Learn everyday.
- Learn yourself.
- Share your knowledge.
- Learn from the past, dream on the future, live and enjoy the present to the max!.
At life:
- Let's act, not complain.
- Be flexible.
At work:
- Let's give solutions, not questions.
- Aim to simplicity not intellectualism.