Put the building of the apps into a foreach loop as is done with the libs
and drivers in the DPDK meson build. This will reduce the path needed to
call the compiled binaries in the build directory by one level, while the
main benefit is reduced code duplication between the different apps.
Bruce Richardson (3):
app: generalize building of apps using meson
app/proc_info: rename folder to remove underscore
app: add all remaining apps to meson build
app/meson.build | 47 +++++++++++++++++++++++++++++++++--
app/pdump/meson.build | 6 +++++
app/{proc_info => proc-info}/Makefile | 0
app/{proc_info => proc-info}/main.c | 0
app/proc-info/meson.build | 6 +++++
app/test-bbdev/meson.build | 9 +++++++
app/test-crypto-perf/meson.build | 14 +++++++++++
app/test-eventdev/meson.build | 15 +----------
app/test-pmd/meson.build | 20 ++-------------
9 files changed, 83 insertions(+), 34 deletions(-)
create mode 100644 app/pdump/meson.build
rename app/{proc_info => proc-info}/Makefile (100%)
rename app/{proc_info => proc-info}/main.c (100%)
create mode 100644 app/proc-info/meson.build
create mode 100644 app/test-bbdev/meson.build
create mode 100644 app/test-crypto-perf/meson.build
--
2.14.3
