Swift build is failing when using Xcode

[TiagoLopes (Tiago Maia)]

I'm trying to build the Swift project on my machine. I'm using the Xcode option and I've followed the instructions on GettingStarted.md.

I've also faced the problems in the following posts:

Failing Tests while Compiling Swift on Xcode 12 with MacOS Big Sur Beta

I am trying to compile Swift for a while now. The compilation goes perfectly but some test case fails which results in the process to terminate with an exit status of 65. I am using Xcode 12 ( not beta ) and macOS Big Sur Beta. I am using this command to build the Swift compiler. utils/build-script --skip-build-benchmarks \ --skip-ios --skip-watchos --skip-tvos --swift-darwin-supported-archs "x86_64" --cmake-c-launcher="$(which sccache)" --cmake-cxx-launcher="$(which sccache)" --release-…

Building Swift compiler from source fails when not using Ninja

Now I got this problem, where the build tried to reference the lib/Debug folder instead of the plain Debug folder: clang: error: no such file or directory: '/Users/philipturner/Documents/Swift-Compiler/swift-project/build/Xcode-DebugAssert/swift-macosx-arm64/lib/Debug/libswiftCompilerModules-bootstrapping1.a' Command Ld failed with a nonzero exit code I opened up the Xcode project and pressed Cmd + B. It seems to have encountered that error just as a warning and continued with the build, so ho…

Configurations of my machine

• A MacBook Pro (Apple m1 pro chip)
• MacOS Monterey (12.2.1)
• Xcode 13.2.1
• cmake version 3.22.3
• Python 3.8.9
• Ninja 1.10.2
• sccache 0.2.13

Command with options

utils/build-script --skip-build-benchmarks \        
  --skip-ios --skip-watchos --skip-tvos --swift-darwin-supported-archs "$(uname -m)" \
  --sccache --release-debuginfo --swift-disable-dead-stripping --test \
  --xcode --skip-test-cmark --bootstrapping=off

Output

The log is pretty big and I wasn't able to create a public gist with the whole output (Github wouldn't create it). Here I'm posting the final parts of it.

From what I understood, it is not able to find the headers of some of the libraries. The errors happen during the test phase.

Ninja

I was able to build the project with Ninja. What is the development flow when using this option? I would like to inspect the standard library. I like the user experience that Xcode offers (that's why I was trying to build it using Xcode).

[philipturner]

@TiagoLopes

I was able to build the project with Ninja. What is the development flow when using this option? I would like to inspect the standard library. I like the user experience that Xcode offers (that's why I was trying to build it using Xcode).

I felt the exact same way when I started with compiler development. But ultimately, Ninja is much more ergonomic and robust than Xcode for this kind of thing. I use Xcode for editing individual source files (by double-clicking them in Finder), but not as the full-fledged IDE with .xcodeproj files. Your best bet may be to learn Ninja despite the learning curve.

I have talked with an expert who manages to use Xcode for debugging the compiler, so it's not entirely impossible.

[filip-sakel]

Many folks (including myself) use VS Code for editing. Here’s a relevant thread: Improving `GettingStarted.md` - #3 by filip-sakel