Features/Kconfig (GSoC 2013): Difference between revisions
Akoskovacs (talk | contribs) No edit summary |
Akoskovacs (talk | contribs) |
||
| Line 3: | Line 3: | ||
The aim of this Google Summer of Code 2013 project is to bring the Linux kernel's Kconfig facility to Qemu, making it much easier to configure at build-time. | The aim of this Google Summer of Code 2013 project is to bring the Linux kernel's Kconfig facility to Qemu, making it much easier to configure at build-time. | ||
[[File:kconfig_main.png| | [[File:kconfig_main.png|200px|frame|An example target configuration]] | ||
[[File:kconfig_x86.png|400px|frame|An example configuration for the i386 target]] | [[File:kconfig_x86.png|400px|frame|An example configuration for the i386 target]] | ||
Revision as of 03:44, 1 July 2013
Summary
The aim of this Google Summer of Code 2013 project is to bring the Linux kernel's Kconfig facility to Qemu, making it much easier to configure at build-time.
An example target configuration
An example configuration for the i386 target
Owner
- Name: Ákos Kovács
- Email: akoskovacs@gmx.com
Implementation
Main topics
- Importing kconfig-frontends to Qemu (at scripts/kconfig)
- New syntactical structures in the Kconfig files (with writing the actual Kconfig files)
- Integrating kconfig to the existing build infrastructure
Progress
At the time, the first and the second topic is in progress. This means, that the kconfig-frontends can be built from the top-level directory (with 'make menuconfig/xconfig/gconfig/...') and has a new syntactical structure. This will enable the user to manage all targets from one root Kconfig file. The current syntax consist a 'symbol' token and the actual symbol itself, which can be written this way:
config TEST
prompt "A foo-bar feature"
symbol TARGET_FOO
default n
However, this is not a fixed syntax and there could be other ways.