GettingStarted.md: avoid preinstalling CMake #83063
Merged
Conversation
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
We're seeing multiple build failures with CMake 4.0: e.g. SwiftPM bootstrapping issues on macOS. `build-script` will always build a fixed version of CMake that's known to work if preinstalled one is not found. Let's reduce the chances for confusion by not recommending preinstalled CMake in `GettingStarted.md`.
Contributor
Author
|
@swift-ci smoke test |
bnbarham
reviewed
Jul 15, 2025
| 1. Install [Ninja][] and [Sccache][]: | ||
| - Via [Homebrew][] (recommended): | ||
| ```sh | ||
| brew install cmake ninja sccache |
Contributor
There was a problem hiding this comment.
See my other comment, can we just pin it instead?
Contributor
Author
There was a problem hiding this comment.
Ditto, the answer is "no" unfortunately
Contributor
Author
|
@swift-ci smoke test macos |
bnbarham
approved these changes
Jul 17, 2025
Contributor
bnbarham
left a comment
bnbarham
left a comment
There was a problem hiding this comment.
Would be nice to get this working, but better to not be confusing for now 👍
Contributor
|
I ran into an issue today. |
Contributor
Author
Which exact commit are you trying to build and on which OS? What's the exact |
Contributor
Author
|
I assume you're building on macOS? That's fixed in #83296, you'll have to re-run |
Contributor
Author
|
Also updating |
Contributor
|
Ah thanks for all the great comments! Yeah I was at the tip of main today so commit |
Contributor
|
@MaxDesiatov I do keep running into an issue that might be related to cmake. I tried setting the CC variable but it doesn't seem to be picked up since the already set path probably has presedence and indeed doesn't contain clang. I ran the following invocation of build-script: Not sure if this was part of the issues with CMake? |
Contributor
Author
|
Can you ensure that the version CMake you're running is the one built by |
Contributor
|
I no longer have cmake installed locally so it should be, but also yeah it mentions I'm not sure which product it is? How do I identify that specifically? Could that be bootstrap or maybe swift-system? Please let me know what I can provide you with :) |
Contributor
|
@MaxDesiatov Here's a larger part of the output I'm seeing hope that helps: So I feel it's trying to build swift-system in order to build swiftpm? |
Contributor
Author
|
Does |
Contributor
|
Ah yeah that was missing from my invocation. Will run it with that now, thanks! |
Contributor
|
That worked! Thanks. The full invocation that worked for me was: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
We're seeing multiple build failures with CMake 4.0: e.g. SwiftPM bootstrapping issues on macOS.
build-scriptwill always build a fixed version of CMake that's known to work if preinstalled one is not found. Let's reduce the chances for confusion by not recommending preinstalled CMake inGettingStarted.md.