meson-python injects a build dependency on ninja if it detects that ninja is not available. Thus it seems that it implicitly assumes that the meson build backed used is exclusively ninja. This is fine. However, the project compilation is initiated with the meson compile -C $builddir command, which is the backend-agnostic way offered by Meson to compile a project. Should this command be replaced by ninja -C $builddir? There isn't much difference, except that invoking ninja directly is potentially much faster. This is relevant for editable wheel installations, where the project rebuild is triggered on import.
meson-python injects a build dependency on
ninjaif it detects thatninjais not available. Thus it seems that it implicitly assumes that the meson build backed used is exclusivelyninja. This is fine. However, the project compilation is initiated with themeson compile -C $builddircommand, which is the backend-agnostic way offered by Meson to compile a project. Should this command be replaced byninja -C $builddir? There isn't much difference, except that invokingninjadirectly is potentially much faster. This is relevant for editable wheel installations, where the project rebuild is triggered on import.