| 39b370a5 | 02-Sep-2019 |
Brad Bishop <bradleyb@fuzziesquirrel.com> |
build: add support for building with meson
Follow the OpenBMC herd and support a more modern, more comprehensible,
more performant build framework.
To build using meson:
meson build
ninja -C bu
build: add support for building with meson
Follow the OpenBMC herd and support a more modern, more comprehensible,
more performant build framework.
To build using meson:
meson build
ninja -C build
ninja -C build install
Maintained support for:
Configurable dbus parameters:
INPUT_HISTORY_BUSNAME_ROOT= -> -Dinput-history-busname-root=
INPUT_HISTORY_SENSOR_ROOT = -> -Dinput-history-sensor-root=
UCD90160 support:
UCD90160_DEF_YAML_FILE= -> -Ducd90160-yaml=
--enable-turn-off-ucd90160-access = -> -Ducd90160-access=
Added -Dtests to match de-facto OpenBMC meson usage conventions.
Dropped UCD90160_DEF_OUTPUT_DIR. Much like the destination of
intermediate artifacts like object files are not configurable, the
location of the generated UCD definition file should not be configurable
either.
Dropped support for --enable-oe-sdk rpath munging. This was a
workaround for broken oe sdks that don't figure out the correct rpath
when running make check or ninja test.
Tested by building with both meson and autotools and then compared build
artifacts from each build system:
generated source code is the same
generated binaries have the same symbols
Ran existing unit tests (which passed) using ninja test.
Change-Id: Iac80ba1fe5c2d01abe0e0a95e0bec03b8b828ef5
Signed-off-by: Brad Bishop <bradleyb@fuzziesquirrel.com>
show more ...
|
| 3c0f8048 | 01-Nov-2017 |
Brandon Wyman <bjwyman@gmail.com> |
Add separator lines between the error entries
To make the YAML file formatting more consistent, and to aid in
readability, add separator lines between the various power supply
errors, as was done wi
Add separator lines between the error entries
To make the YAML file formatting more consistent, and to aid in
readability, add separator lines between the various power supply
errors, as was done with the power sequencer errors.
Change-Id: Ib81ff0c7dbbc20a408d5e22a15ed542ef1902289
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
show more ...
|
| 02bc0f2f | 01-Nov-2017 |
Brandon Wyman <bjwyman@gmail.com> |
Remove the PowerSupplyUnderVoltageFault error
Since the VIN_UV_FAULT check was combined with the INPUT_FAULT_WARN
check, we no longer need this error. However, since they are now
combined, update th
Remove the PowerSupplyUnderVoltageFault error
Since the VIN_UV_FAULT check was combined with the INPUT_FAULT_WARN
check, we no longer need this error. However, since they are now
combined, update the wording on PowerSupplyInputFault to indicate that
it could be due to an undervoltage condition.
Add a trailing clarification statement to check the cables and/or the
power source to the power supply, to avoid confusion now that we have
added the power supply to the call out.
Change-Id: I5bb0285ee1f2f866ad92decf8e679b26bff3f06f
Signed-off-by: Brandon Wyman <bjwyman@gmail.com>
show more ...
|