I was trying to figure out why the Swift/C++ interop pieces of the toolchain apparently did not ship with support for macCatalyst in Xcode 15.4 and Xcode 16.
Checking the CMake code, it doesn't seem to be enable. After a couple of back and forth and trying to understand the differences between "zippered", "macos-like" and "ios-like" (I still don't understand), I hit another problem with libswiftPrivate.dylib that did not seem created by my changes.
I stashed my changes, clean the build directory and started again, and I hit the same problem:
FAILED: lib/swift/macosx/x86_64/libswiftSwiftPrivate.dylib
...
ld: building for 'zippered(macOS/Catalyst)', but linking in object file (/Users/danielrodriguez/code/swift-source/build/my_macos/swift-macosx-arm64/stdlib/private/SwiftPrivate/OSX/x86_64/SwiftPrivate.o) built for 'macOS'
clang++: error: linker command failed with exit code 1 (use -v to see invocation)
My build script invocation is the following:
utils/build-script --build-subdir=my_macos --assertions --swift-enable-ast-verifier=0 --compiler-vendor=apple --sccache --release-debuginfo --swift-disable-dead-stripping --swift-enable-experimental-string-processing --test --validation-test --skip-test-swift --skip-test-libicu --skip-test-lldb --skip-test-foundation --skip-test-libdispatch --skip-test-xctest --skip-test-llbuild --skip-test-swiftpm --skip-test-cmark --skip-build-benchmarks --skip-build-tvos --skip-build-watchos --maccatalyst
Has someone been able to build with the --maccatalyst option lately?