Provides support for generating pkg-config files. More...
- autoDetect : bool
- cflagsEntry : stringList
- conflictsEntry : stringList
- customVariables : string
- excludedDependencies : stringList
- fileName : string
- libsEntry : stringList
- libsPrivateEntry : stringList
- nameEntry : string
- requiresEntry : stringList
- requiresPrivateEntry : stringList
- transformFunction : var
- urlEntry : string
- versionEntry : string
|1.12.0||This tag is attached to the generated |
If this property is enabled, then Qbs will try to derive various
.pc file entries from the contents of the product's Export item, including the dependencies declared therein. Values for these fields can still be explicitly provided via the respective properties, in which case they will be concatenated with the auto-detected ones. If an exported dependency is known to correspond to a pkg-config module (either by pulling in the
Exporter.pkgconfig module or by appearing in the requiresEntry property), it will end up in the
Requires field of the
.pc file, otherwise its exported cpp properties will be collected for use in the
Libs fields. The excludedDependencies property can be used to ignore specific products altogether.
Use this property to add arbitrary variable assignments into the
.pc file. The property is a map that will produce one assignment per entry. The keys and values of the map represent the left-hand sides and right-hand sides of these assignments, respectively. The values are strings that will be written into the file verbatim.
If autoDetect is enabled, the entries of this property will be matched against the product's exported dependencies. In case such a dependency's name is present in the array, Qbs will not traverse that dependency to collect entries for the
This list must not contain any values that are present in requiresEntry.
The file name of the generated pkg-config metadata file.
product.targetName + ".pc"
The value of the
Requires field in the
If autoDetect is enabled, then those of the product's exported dependencies that pull in the
Exporter.pkgconfig module will also end up in the
Requires field, provided they are not listed in excludedDependencies.
If an exported dependency matches an entry of this array, Qbs will not traverse that dependency to gather cpp properties for use in the cflagsEntry and libsEntry values, as pkg-config takes care of that itself.
A function with the signature
function(product, moduleName, propertyName, value). This can be useful to "fine-tune" property values if autoDetect is enabled, in case they need amending for the purpose of pkg-config. The
product parameter represents the exporting product, the remaining parameters describe the module property. The modified value of the module property shall be returned.
© 2022 The Qt Company Ltd. Documentation contributions included herein are the copyrights of their respective owners. The documentation provided herein is licensed under the terms of the GNU Free Documentation License version 1.3 as published by the Free Software Foundation. Qt and respective logos are trademarks of The Qt Company Ltd in Finland and/or other countries worldwide. All other trademarks are property of their respective owners.