Friedrich W. H. Kossebau 0985d48d92 [FEATURE] Option to build & install QCH file with the public API dox Using the new extra-cmake-modules module ECMAddQch (since 5.36.0) this adds the option to automatically build and install a file in QCH format with the docs about the public API, which then can be used e.g. in Qt Assistant, Qt Creator or KDevelop. Additionally the installed cmake config files will be extended with a target KF5Config_QCH containing information about how to "link" into the generated QCH file, which then can be used in the cmake build system of other libraries building on this library, by simply listing this target in "LINK_QCHS" of their ecm_add_qch() usage. And a respective doxygen tag file with all the metadata about the generated QCH file and used for the "linking" will be created and installed. Pass -DBUILD_QCH=ON to cmake to enable this.		9 years ago
autotests	tests: use QIODevice::Text in kconfigcompiler_test	9 years ago
cmake	KConfig: stop exporting and installing KConfigBackend.	9 years ago
docs	Add support for get QStandardPaths locations.	10 years ago
src	[FEATURE] Option to build & install QCH file with the public API dox	9 years ago
.reviewboardrc	Add myself to the target people to receive all review requests.	12 years ago
CMakeLists.txt	[FEATURE] Option to build & install QCH file with the public API dox	9 years ago
COPYING.LIB	Move kconfig code to the root directory.	12 years ago
DESIGN	Move kconfig code to the root directory.	12 years ago
KF5ConfigConfig.cmake.in	[FEATURE] Option to build & install QCH file with the public API dox	9 years ago
KF5ConfigMacros.cmake	Make sure we don't break compilation with past broken units	9 years ago
README.md	Add/update first line of README.md to be a short description, useful for inqlude	11 years ago
TODO	Move kconfig code to the root directory.	12 years ago
metainfo.yaml	Add FreeBSD to metainfo.yaml.	9 years ago

README.md

KConfig

Persistent platform-independent application settings.

Introduction

KConfig provides an advanced configuration system. It is made of two parts: KConfigCore and KConfigGui.

KConfigCore provides access to the configuration files themselves. It features:

Code generation: describe your configuration in an XML file, and use `kconfig_compiler to generate classes that read and write configuration entries.
Cascading configuration files (global settings overridden by local settings).
Optional shell expansion support (see [docs/options.md](@ref options)).
The ability to lock down configuration options (see [docs/options.md](@ref options)).

KConfigGui provides a way to hook widgets to the configuration so that they are automatically initialized from the configuration and automatically propagate their changes to their respective configuration files.