To assist in packaging and make the installation process a bit more predictable (I can read Makefiles, but I don't like to read Makefiles…) I've created a build system for bees using meson.
As best I can tell, it correctly builds the applications, documentation, and runs tests. If you use meson configure --sysconfdir=/etc --prefix=/usr then it will match the install locations of the current make install.
Some options are provided (see meson_options.txt) to allow enabling/disabling some optional features - generating html documentation, installing systemd unit files, and installing the extra fiemap and fiewalk tools.
Some of the file generation that was previously done with sed and shell in the makefiles is done with python scripts in the meson build. Since meson is present, we're guaranteed to have a python, and it is a bit easier to work with external scripts in the meson build system then attempt to do inline shell.
To assist in packaging and make the installation process a bit more predictable (I can read Makefiles, but I don't like to read Makefiles…) I've created a build system for bees using meson.
As best I can tell, it correctly builds the applications, documentation, and runs tests. If you use
meson configure --sysconfdir=/etc --prefix=/usrthen it will match the install locations of the currentmake install.Some options are provided (see
meson_options.txt) to allow enabling/disabling some optional features - generating html documentation, installing systemd unit files, and installing the extrafiemapandfiewalktools.Some of the file generation that was previously done with sed and shell in the makefiles is done with python scripts in the meson build. Since meson is present, we're guaranteed to have a python, and it is a bit easier to work with external scripts in the meson build system then attempt to do inline shell.