#
a47e082e |
| 03-Jan-2024 |
Andrew Jeffery <andrew@codeconstruct.com.au> |
subprojects: Bump boost to 1.83
Bump to avoid issues such as the following:
``` In file included from ../src/Utils.hpp:3, from ../src/Thresholds.hpp:3, from ../src
subprojects: Bump boost to 1.83
Bump to avoid issues such as the following:
``` In file included from ../src/Utils.hpp:3, from ../src/Thresholds.hpp:3, from ../src/sensor.hpp:6, from ../src/PwmSensor.hpp:3, from ../src/PwmSensor.cpp:17: ../src/VariantVisitors.hpp:18:10: fatal error: boost/type_index.hpp: No such file or directory 18 | #include <boost/type_index.hpp> | ^~~~~~~~~~~~~~~~~~~~~~ ```
1.83 is used by openbmc/openbmc@43471c8c565d346c1727ba2360db373035234c26
With the bump I can now successfully build dbus-sensors on Debian Bookworm with `meson setup --cross-file=gcc-13 build`[1], even if boost libraries and headers of varying version are installed via `apt`.
[1]: https://amboar.github.io/notes/2023/09/12/unstable-gcc-on-debian-stable.html
Change-Id: I43cb95167ede3271cc6ce6ea6ea5421911b575c0 Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
show more ...
|
#
1d7b4788 |
| 03-Jan-2024 |
Andrew Jeffery <andrew@codeconstruct.com.au> |
meson: Improve boost integration
Currently we hit the following:
``` $ meson setup --force-fallback-for=boost build ... WARNING: Subproject 'boost' did not override 'boost' dependency and no variab
meson: Improve boost integration
Currently we hit the following:
``` $ meson setup --force-fallback-for=boost build ... WARNING: Subproject 'boost' did not override 'boost' dependency and no variable name specified Dependency boost from subproject subprojects/boost found: NO meson.build:57: WARNING: include_directories sandbox violation! The project is trying to access the directory 'subprojects/boost_1_79_0/' which belongs to a different subproject. This is a problem as it hardcodes the relative paths of these two projects. This makes it impossible to compile the project in any other directory layout and also prevents the subproject from changing its own directory layout.
Instead of poking directly at the internals the subproject should be executed and it should set a variable that the caller can then use. Something like:
# In subproject some_dep = declare_dependency(include_directories: include_directories('include'))
# In subproject wrap file [provide] some = some_dep
# In parent project some_dep = dependency('some') executable(..., dependencies: [some_dep])
This warning will become a hard error in a future Meson release.
meson.build:57:14: ERROR: Include dir subprojects/boost_1_79_0/ does not exist. ```
Address the sandbox violation and reduce the amount of configuration noise in meson.build by providing an appropriate wrap via packagefiles.
Change-Id: I4063764d2c3a00f58d3c83712092303538b64843 Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
show more ...
|
#
16966b55 |
| 15-Sep-2021 |
Ed Tanous <edtanous@google.com> |
Enable an io-uring build
There exists a bug where calls that we previously thought were non-blocking, actually do block when used with hwmon or filesystem fds. This causes high latencies on the dbus
Enable an io-uring build
There exists a bug where calls that we previously thought were non-blocking, actually do block when used with hwmon or filesystem fds. This causes high latencies on the dbus interfaces when lots of sensors are used in a single daemon, as is the case in PSUSensor.
This patchset moves the PSUSensor code over to using io-uring, through boost asio, using the random_access_file class. This helps with performance in a number of ways, the largest of which being that sensor reads are no longer blocking.
Tested:
Booted the sensor system on Tyan S7106; dbus-monitor shows sensors scanning normally.
Signed-off-by: Ed Tanous <edtanous@google.com> Change-Id: I654eafcfab5a24b65b89c204ab43d81c7ae064cf
show more ...
|