seL4/include/plat
Adrian Danis f6ae69f0f0 Use autoconf generated header for standalone kernel builds
Configuring standalone kernel builds (such as those used by verification)
has been done in a completely different way to how the kernel is
configured for project builds. As the kernel gains additional options
it becomes difficult to maintain standalone kernel builds without
tediously exporting these additional options, such tedious work is
what autoconf.h is meant to address

The new configuration strategy requires a include/plat/PLAT/autoconf.h
file to exist for any platform that wants to hae standalone builds
performed on it. This configuration also becomes the *verified*
configuration, and makes it clear for projects to build the kernel
in the verified configuration.
2015-11-09 14:41:18 +11:00
..
allwinnerA20/plat xIntroduce RELEASE_PRINTF, which allows a renamed printf (release_printf) to be used in a release build of the kernel - userful for debugging tests that only fail on a release build of the kernel 2015-08-03 10:26:41 +10:00
am335x Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
apq8064 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
exynos4 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
exynos5 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
imx6 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
imx31 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
omap3 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
pc99 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00
zynq7000 Use autoconf generated header for standalone kernel builds 2015-11-09 14:41:18 +11:00