wilderjds
/
kconfig
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
30 Commits
1 Branch
0 Tags
1.1 MiB
 
 
 
 
Tag: Branch: Tree: 9e3d22c3f5
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '9e3d22c3f5'
${ noResults }
Go to file
Alex Richardson 9e3d22c3f5
Print the diff to stdout on comparison failure 		12 years ago
autotests Print the diff to stdout on comparison failure 12 years ago
docs Use kde5rc instead of kde4rc naming convention, REVIEW: 114917 12 years ago
src Use the new syntax for ecm_generate_headers() 12 years ago
.reviewboardrc Add .reviewboardrc 12 years ago
CMakeLists.txt Use ecm_configure_package_config_file 12 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 Move kconfig code to the root directory. 12 years ago
KF5ConfigMacros.cmake rename kconfig_compiler to kconfig_compiler_kf5 12 years ago
README.md Update REAMDE 12 years ago
TODO Move kconfig code to the root directory. 12 years ago
kconfig.yaml Add README.md and yaml files 12 years ago

README.md

KConfig

Backend for storing application configuration

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:

  • centralized definition: define your configuration in an XML file and use kconfig_compiler to generate classes to read and write configuration entries.

  • lock-down (kiosk) support.

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.

Links