This PR updates the steps for configuring and building mavlink-router to use meson/ninja. The actual installation of the mavlink-routerd binary is done by simply copying it from the build directory to its installation destination.
This final step of copying the binary into its destination folder replaces the standard way of installing mavlink-router (sudo ninja -C build install) because ninja installs the service into systemd by default and requires admin rights to do it. This request for admin rights is done through "polkit" which requires manual entry of the admin password which fails through puppet. Also, it does not seem to be possible to disable the installation of the service in systemd as it was possible with the --disable-systemd argument in autogen.sh, so the installation step is actually not desired.
Hi, the old method of installing mavlink-router via the
autogen.shscript is deprecated since November 2021 (see https://github.com/mavlink-router/mavlink-router/commit/c8c7c1c). Mavlink-router is now configured and built using meson/ninja.This PR updates the steps for configuring and building mavlink-router to use meson/ninja. The actual installation of the
mavlink-routerdbinary is done by simply copying it from the build directory to its installation destination.This final step of copying the binary into its destination folder replaces the standard way of installing mavlink-router (
sudo ninja -C build install) because ninja installs the service into systemd by default and requires admin rights to do it. This request for admin rights is done through "polkit" which requires manual entry of the admin password which fails through puppet. Also, it does not seem to be possible to disable the installation of the service in systemd as it was possible with the--disable-systemdargument inautogen.sh, so the installation step is actually not desired.This was tested on an Nvidia Xavier NX Dev Kit.