Talk:Ninja (build system)

This article was nominated for deletion on August 1 2013. The result of the discussion was delete.

Computing: Software / Free and open-source software Low‑importance

	This article is within the scope of WikiProject Computing, a collaborative effort to improve the coverage of computers, computing, and information technology on Wikipedia. If you would like to participate, please visit the project page, where you can join the discussion and see a list of open tasks.ComputingWikipedia:WikiProject ComputingTemplate:WikiProject ComputingComputing articles
Low	This article has been rated as Low-importance on the project's importance scale.
	This article is supported by WikiProject Software (assessed as Low-importance).
	This article is supported by Free and open-source software (assessed as Low-importance).

Can someone add more examples please[edit]

Can someone add more examples for ninja build? Projects that use it for example.

Only Google Chrome... that is a big project but only one. 2A02:8388:1641:3580:BE5F:F4FF:FECD:7CB2 (talk) 19:15, 6 July 2017 (UTC)[reply]

Gentoo Linux builds cmake-based projects with Ninja by default when emerging packages. --L3u (talk) 09:54, 27 September 2019 (UTC)[reply]

let's talk capability[edit]

Without depends checking (which make does awfully unless written by an expert in which case it is perfect and speedier than anything else) why not use a bourne shell? Fast and capable, allows awk. all IEEE tools and standardized for eons. "cc *.c" works fine.

A "quick make" sounds cool. i hope there are not versional problems and demands for continual upgrading and depends on installing ninja (projects ninja itself is built using?) because that would not be simple.

What ninja and the terribly SLOW cmake don't help any with is (if we are talking efficiency) is LIBRARY MANAGEMENT, object management ar(1) ld.so(1) which still remains pervasive on all platforms today. To make matters worse, some projects are using hacky .py .pl to sift sybols using a "language which themselves have heavy dependencies to build" (so are not available on a platform until much later). And just awful - those two languages are famous for "making non-IEEE changes that break past code bases", so, scripts that filter library symbols break.

Just saying. There is still no library in the sky pie. — Preceding unsigned comment added by 2601:143:480:A4C0:BD2B:444D:D946:4A4E (talk) 02:47, 8 April 2021 (UTC)[reply]