summaryrefslogtreecommitdiffstats
path: root/meta-skeleton/recipes-core/busybox
diff options
context:
space:
mode:
authorNathan Rossi <nathan@nathanrossi.com>2019-04-03 05:37:02 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2019-04-09 13:44:39 +0100
commit9e685e2591c81c28c4fe27d8554af78b52f3a1dc (patch)
tree94a2aa04157a65271678033f08ff5b01bcfb63a0 /meta-skeleton/recipes-core/busybox
parent5da6073d47dcdc335d5c225a8945f5f85609580e (diff)
downloadpoky-9e685e2591c81c28c4fe27d8554af78b52f3a1dc.tar.gz
ccmake.bbclass: Create a cml1 style class for the CMake curses UI
The ccmake bbclass implements two tasks. The first task 'ccmake' preserves the configured state of CMakeCache.txt (generated from the configure task) and invokes the 'ccmake' program within a oe_terminal execution. The user can then review, select and modify configuration options and once satisfied with the configuration exit ccmake. Once ccmake has exited the build can be run and the updated configuration should be reflected in the output build. The ccmake bbclass has a second task 'ccmake_diffconfig' to compute the differences in configuration which was modified by ccmake. Since there are many ways to persist the configuration changes within recipes and layer configuration, the differences are emitted as a bitbake recipe fragment (configuration.inc) using EXTRA_OECMAKE as well as a CMake script file which can be used as a input to cmake via the '-C' argument. Both files are generated in the WORKDIR of the build and the paths to the files are written as output from the build. It is then up to the user to take this configuration and apply it to the desired location. (From OE-Core rev: 091c46a8ecba6b6b7c44078ae2b567a2ef6e72e9) Signed-off-by: Nathan Rossi <nathan@nathanrossi.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-skeleton/recipes-core/busybox')
0 files changed, 0 insertions, 0 deletions