Build on macOS fails when Xcode at non-standard path

[humblehacker]

I'm attempting to build zed from source, and I'm getting a number of failures that look like this:

error: linking with `cc` failed: exit status: 1
  |
  = note:  "cc" "/var/folders/zd/t1qx67ys2c167h4zxyrkql0h0000gn/T/rustcPDOqS5/symbols.o" "<2 object files omitted>" "/Users/david/src/ext/zed/target/debug/deps/{libversion_check-431f609e7f250c6b.rlib}.rlib" "<sysroot>/lib/rustlib/aarch64-apple-darwin/lib/{libstd-*,libpanic_unwind-*,libobject-*,libmemchr-*,libaddr2line-*,libgimli-*,librustc_demangle-*,libstd_detect-*,libhashbrown-*,librustc_std_workspace_alloc-*,libminiz_oxide-*,libadler2-*,libunwind-*,libcfg_if-*,liblibc-*,liballoc-*,librustc_std_workspace_core-*,libcore-*,libcompiler_builtins-*}.rlib" "-lSystem" "-lc" "-lm" "-arch" "arm64" "-mmacosx-version-min=11.0.0" "-L" "/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib" "-o" "/Users/david/src/ext/zed/target/debug/build/generic-array-8ef3ffdc416b357e/build_script_build-8ef3ffdc416b357e" "-Wl,-dead_strip" "-nodefaultlibs"
  = note: some arguments are omitted. use `--verbose` to show all linker arguments
  = note: ld: warning: search path '/Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk/usr/lib' not found
          ld: library 'System' not found
          cc: error: linker command failed with exit code 1 (use -v to see invocation)

Notice that it's expecting to find Xcode in the usual /Applications/Xcode.app path. However, I've usually got multiple versions of Xcode installed and I always rename them e.g Xcode-16.4.app - there is no Xcode.app on my machine.

For reference, on my machine currently:

xcode-select -p	/Applications/Xcode-16.4.app/Contents/Developer
xcrun --show-sdk-platform-path	/Applications/Xcode-16.4.app/Contents/Developer/Platforms/MacOSX.platform
xcrun --show-sdk-path	/Applications/Xcode-16.4.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX.sdk

I've even tried setting DEVELOPER_DIR before running cargo run, but that didn't help.

---

Can anyone help me track this down? I've done quite a bit of searching but I don't know enough about the rust build system to know where to look.