New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
gnumake3: remove #37658
Merged
Merged
gnumake3: remove #37658
Changes from all commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
14 changes: 0 additions & 14 deletions
14
pkgs/development/tools/build-managers/gnumake/3.82/MAKEFLAGS-reexec.patch
This file was deleted.
Oops, something went wrong.
48 changes: 0 additions & 48 deletions
48
pkgs/development/tools/build-managers/gnumake/3.82/archives-many-objs.patch
This file was deleted.
Oops, something went wrong.
71 changes: 0 additions & 71 deletions
71
pkgs/development/tools/build-managers/gnumake/3.82/construct-command-line.patch
This file was deleted.
Oops, something went wrong.
58 changes: 0 additions & 58 deletions
58
pkgs/development/tools/build-managers/gnumake/3.82/copy-on-expand.patch
This file was deleted.
Oops, something went wrong.
17 changes: 0 additions & 17 deletions
17
pkgs/development/tools/build-managers/gnumake/3.82/darwin-library_search-dylib.patch
This file was deleted.
Oops, something went wrong.
62 changes: 0 additions & 62 deletions
62
pkgs/development/tools/build-managers/gnumake/3.82/default.nix
This file was deleted.
Oops, something went wrong.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add ninja, it is usually faster than make.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd think that in the context of Nix, make vs. ninja wouldn't make much difference. Ninja is certainly faster at determining that nothing needs to be done, but when you are building the project for the first time, and Ninja hasn't built up its databases yet, then I'd be surprised if the build time were changed significantly.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I measured it and both ninja and make back-ends seem to average slightly above five seconds on my machine. For larger codebases, though, ninja is significantly faster even when building from scratch according to my experiments. http://voices.canonical.com/jussi.pakkanen/2012/02/28/speed-bumps-hide-in-places-where-you-least-expect-them/ agrees with my observations.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think that individual packages built with CMake should switch to Ninja without a good reason; however I'd mildly approve switching all CMake projects in Nixpkgs to Ninja by default. The upsides of Ninja are possibly faster build, more concise output, better debugability (especially with issues of parallel building) due to the ability to query the build graph, but an irksome downside is that console output (compiler warnings and errors) is not colorized.