ninja macros

[Elan Ruusamäe]

why is invoking ninja hidden behind these macros?


%build
%meson build
%meson_build -C build

%install
rm -rf $RPM_BUILD_ROOT
%meson_install -C build


i.e %meson_build and %meson_install expand to ninja, just have %ninja
macro out there?


or at least %ninja_build and %ninja_install

[Neal Gompa]

Post by Elan Ruusamäe
why is invoking ninja hidden behind these macros?
%build
%meson build
%meson_build -C build
%install
rm -rf $RPM_BUILD_ROOT
%meson_install -C build
i.e %meson_build and %meson_install expand to ninja, just have %ninja
macro out there?
or at least %ninja_build and %ninja_install

I'm fairly certain that the upstream meson macros wrap %ninja_build
and %ninja_install because it's entirely possible for another backend
to replace ninja in meson in the future.

But the behavior you're describing doesn't look like the upstream macros...