commit | a3ab4d90d658752c48f1a74ef9003f624f66e81e | [log] [tgz] |
---|---|---|
author | Brad Bishop <bradbish@qti.qualcomm.com> | Wed Jul 09 16:24:23 2025 -0400 |
committer | Brad Bishop <bradbish@qti.qualcomm.com> | Tue Jul 29 09:17:42 2025 -0400 |
tree | 3431fdadad0826e1d6e9119ec8a2c4a9190048e6 | |
parent | fcae52617d56810ab6083395bd2d11073b175b19 [diff] |
meson: use gtest from meson wrapdb There's little point in introducing potential gtest development instability into our unit testing. Download gtest from the meson wrapdb and use that verbatim. Use the same version as openbmc-build-scripts. Tested by building and running the unit tests using the gtest subproject. Change-Id: I1ecc28f233dd3dc22d3ee5923e9c8f0fabec2500 Signed-off-by: Brad Bishop <bradbish@qti.qualcomm.com>
This repository contains the mapper, which assists in finding things on D-Bus. There is documentation about it in the docs repository.
Non-OpenBMC build dependencies are:
meson build && ninja -C build
meson build && ninja -C build test
rm -rf build