Package Details: ninja-kitware 1.11.1-1

Git Clone URL: (read-only, click to copy)
Package Base: ninja-kitware
Description: Small build system with a focus on speed - Kitware version with JobServer and Fortran compatibility
Upstream URL:
Licenses: Apache
Conflicts: ninja
Provides: ninja
Submitter: phcerdan
Maintainer: phcerdan
Last Packager: phcerdan
Votes: 3
Popularity: 0.000080
First Submitted: 2018-05-23 15:37 (UTC)
Last Updated: 2023-03-20 12:28 (UTC)

Required by (1896)

Sources (1)

Latest Comments

phcerdan commented on 2022-06-30 19:29 (UTC)

You can get more information about the make-style jobserver support from this issue: Check associated PRs, and commits from other repos (including the Kitware branch) referencing it. Hope it helps.

newsboost commented on 2022-06-30 17:48 (UTC)

Hi @phcerdan: I'm not so experienced with these things, might I ask: How do I know if a project uses "make-style jobserver support"? I saw some tickets back from 2016 about this, so I'm worried if the original ninja has some newer features that are better, despite lack of "make-style jobserver support", could you please comment on that? Or is the jobserver support automatically in use by "make -j"? hmm. Maybe I should just time a project using ninja, that I have with and without kitware (but I lack an understanding of this feature, so I hope it's okay to ask here, for better understanding the difference between these 2 ninja-options)...

phcerdan commented on 2022-06-30 14:37 (UTC)

Hi @newsboost, thanks for the comment. Indeed, most of the features from the Kitware branch have been merged upstream, the only pending is: make-style jobserver support. Which is the one I use the most.

The Kitware branch is not dead and this aur will follow it until the branch is archived.

newsboost commented on 2022-06-30 14:21 (UTC)

Hi, I just noticed that is at version 1.11.0 while is at 1.10.2. Furthermore it seems not much development is going on in the kitware-branch and at least some of the Fortran-functionality has been merged. The kitware-branch seems very quiet, almost dead compared to the upstream branch. I haven't tried it, but maybe it's about time to use community/ninja instead of aur/ninja-kitware, any thoughts about this or am I wrong?

simonfxr commented on 2019-02-06 12:05 (UTC)

Sounds good to me, thank you phcerdan.

phcerdan commented on 2019-02-04 17:27 (UTC)

Updated to latest release, and also make emacs optdepends.

Not sure if the way I am handling the optdependency is standard, but seems to work. It will only compile and install the .el files if the executable emacs is present in the system at build time.

I created this PKGBUILD following ninja in community, which still has the emacs-nox.

Let me know if this works for you @simonfxr

phcerdan commented on 2019-02-01 14:28 (UTC)

Thanks simonxfr, I bluntly adapted the PKGBUILD from ninja-git, and they have changed it already. I will update soon.

simonfxr commented on 2019-02-01 14:22 (UTC)

Please do not directly builddepend on emacs-nox, this makes it impossible to install when emacs is present. Just depend on emacs, emacs-nox provides emacs.