Running install target with root privilages breaks Ninja builds
A "common pattern" for a library is to run make
and then sudo make install
. This works splendidly with CMake. However, when using Ninja as the underlying build system, sudo ninja install
changes the owner of .ninja_log
to root. Subsequent invocations of ninja
than fail with
ninja: error: opening build log: Permission denied
Just deleting the file afterwards seems fine, but this is not the way to go, right?