IssueRaiser

I'm obviously aware that ccache solves the mtime problem which is why I find disingenious to say that switching branches with ninja is "t...

I'm obviously aware that ccache solves the mtime problem which is why I find disingenious to say that switching branches with ninja is "totally unusable". Therefore my question. Hash-aware build systems like bazel, if that's what you're imputing, are a nightmare to work with and come with their own set of problems which make it much less appealing to work with than (some) limitations found in cmake+ninja

Posted by menaerus on Mar 30, 2026, 7:56 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.2,000 issues0 comments

ux (Other)

I'm obviously aware that ccache solves the mtime problem which is why I find disingenious to say that switching branches with ninja is "t...

menaerusMar 30, 2026, 7:56 PM

I'm obviously aware that ccache solves the mtime problem which is why I find disingenious to say that switching branches with ninja is "totally unusable". Therefore my question. Hash-aware build systems like bazel, if that's what you're imputing, are a nightmare to work with and come with their own set of problems which make it much less appealing to work with than (some) limitations found in cmake+ninja

Comments (0)

No comments yet. Start the discussion.

Comment on this issue