CI: build in parallel - #242
Merged
Merged
Conversation
cmake --build defaults to a single job under the Makefiles generator, so these builds used one core regardless of how many the machine has. --parallel lets CMake pick the job count; it is a no-op where the generator already parallelises.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
cmake --builddefaults to a single job under the Makefiles generator, so these builds compiled on one core no matter how many the machine has.--parallellets CMake choose the job count. It is a no-op where the generator already parallelises (Ninja), so it is safe to apply uniformly.Test targets are left alone — running tests in parallel is a separate decision.