Xavier Claessens

I imagine this happens with monorepos that could have nothing at the root and subdir for each individual project. In that case I would rather add a meson.build at the...

This is of course not foolproof by any mean. The compiler exe could be wrapper script and we won't detect changes for the real compiler. If the compiler is a...

> If the compiler is a symlink it won't detect if the symlink changed. Note that alternatively I could remove `os.path.realpath()`, that probably would be more consistent with custom_target() that...

Better error reporting is always great. Played a bit with wrong statements in `if` condition, the problem is not limited to assignment: - `if message('hello')` -> `ERROR: Cannot perform 'if'...

Your C compiler for build machine failed sanity checks: ``` Sanity check compile stderr: ld: library not found for -lSystem clang: error: linker command failed with exit code 1 (use...

Can you try setting `build.c_args` option instead, I'm wondering if using a native file confuses Meson.

> Maybe this should be called `is_parallel` to match the signature of `test`. I agree the term `console` seems to be leaking ninja specific implementation. It also very badly describe...

> There's no fundamental objective to preventing parallelism. Currently run_target disabled parallelism as a _**side effect**_ of setting a ninja option that is intended to "guarantee that a target which...

> But you say that you see it contrary to the ninja documentation. Okay, let's roll with that. So -- who is it that specifically wants run_target to not run...

> This is totally bogus, because what you actually want is for ninja to have GNU make jobserver/client support I wouldn't say it's "totally bogus" just because there might be...