While the meson.log file in each build directory contains lots of information, much of it is not of interest to developers, and it can be hard to see the explicitly messages from the dpdk build files among all the rest of the content. Futhermore, while at the end of the a configuration run we print out the list of enable/disabled components, this is never recorded anywhere for anyone who wants to check that build configuration later.
This patchset attempts to solve these issues by supporting a dpdk-meson.log file in each DPDK build folder containing the output from the DPDK meson.build files - including the final summary information for later checking. Bruce Richardson (3): build: add a dpdk-specific meson log file build: shorten top-level build file build: write messages to dpdk build log file app/test/meson.build | 2 +- buildtools/meson.build | 1 + buildtools/write-log-entry.py | 23 +++++++++++++++++++++++ config/arm/meson.build | 2 ++ config/meson.build | 18 ++++++++++++++++++ config/x86/meson.build | 2 ++ drivers/meson.build | 8 +++++--- examples/meson.build | 1 + lib/meson.build | 8 +++++--- meson.build | 31 ++++++++++++------------------- 10 files changed, 70 insertions(+), 26 deletions(-) create mode 100644 buildtools/write-log-entry.py -- 2.25.1
