Roadmap for supporting other Kconfig/Kbuild projects

[paulgazz]

See #235 for more discussion.

Currently, klocalizer and kismet is setup for Linux, but the underlying tooling should be able to work on other systems, e.g., BusyBox. BusyBox, toybox, and axtls have worked in the past.

Candidates:

• BusyBox
• buildroot
• toybox
• axtls
• zephyr (though only older versions I believe)
• Freetz-ng
• Fiasco
• uClibC-ng
• Coreboot (per @ChristianKaltenecker, but this only works with a script that expands the wildcard symbol in source paths, such as src/*/Kconfig; see https://github.com/coreboot/coreboot/blob/master/src/Kconfig#L605)
• Embtoolkit (per @ChristianKaltenecker, this doesn't work right now, because of some error while executing kclause)

[ChristianKaltenecker]

Hey @paulgazz, I also tried kextract, kclause, and klocalizer on other systems. These are:

• Freetz-ng
• Fiasco
• uClibC-ng
• Coreboot (but this only works with a script that expands the wildcard symbol in source paths, such as src/*/Kconfig; see https://github.com/coreboot/coreboot/blob/master/src/Kconfig#L605)
• Embtoolkit (this doesn't work right now, because of some error while executing kclause)

In the end, I was able to extract a dimacs and an smt file for all these projects except for Embtoolkit. For each of this systems, I have used the most current release.

I can also confirm that kextract, kclause, and klocalizer (as described in #235) work for:

• BusyBox
• buildoot
• toybox
• axtls

[paulgazz]

Thanks so much, @ChristianKaltenecker !

[ekuiter]

thanks @ChristianKaltenecker, we (Thomas Thüm's and Gunter Saake's group) also did work with some of these projects (good catch regarding coreboot). (also see my comment on #235)