git_admin/obsidian-vault
1
0 Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

[2026-10-16] eagle: work/projects/vscode-migration/tech-design-xcode-build-server.md work/projects/vscode-migration/vscode-migration.md work/projects/vscode-migration/xcode-build-server.md

Browse Source
This commit is contained in:
Alexey Martemyanov committed 2026-10-16 00:57:55 +06:00
1 parent d333e88688
commit 0ff32c89a7
3 files changed
+142 -10
Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

work/projects/vscode-migration/tech-design-xcode-build-server.md
+8
View File
@@ -5,6 +5,14 @@
**Stakeholders:** macOS and iOS teams
**Project:** [Migration to fully VSCode-supported builds&debugging](https://app.asana.com/1/137249556945/project/1203301625297703/task/1209808486380252) / https://app.asana.com/1/137249556945/project/1203301625297703/task/1219079700626622?focus=true
## Local implementation status — 2026-10-16
The personal [mallexxx/sourcekit-xcode-bsp fork](https://github.com/mallexxx/sourcekit-xcode-bsp) carries the fixes and committed dependency pins at `afd0e3dd026b3ee3619e2271809debee25fec96f`; 58 tests and strict SwiftLint pass. A shared local Git `post-checkout` hook is active, and the setup has been applied and structurally verified in all 97 registered worktrees, including two adjacent checkouts.
The bootstrap/templates live at `/Users/admin/DuckDuckGo/apple-browsers.git/.vscode-local/`; generated setup files use shared local exclusions. The old configurations in `exp` and `sweetpad` were backed up and migrated. `exp/buildServer.json` was already tracked, so that one migration is an intentional uncommitted local modification. No app-repository commits, upstream PRs or issues were created. The DuckDuckGo-owned fork and team/repository rollout described below remain proposed.
Deployment paths, maintenance commands, verification evidence, publishing limitations and cache research: [[projects/vscode-migration/xcode-build-server]].
## Background & Requirements
- Some of us (would prefer to) spend much of the day outside Xcode: in VS Code, reviewing changes, working with AI agents, or across several worktrees at once. There, the Swift language server has no build information for our Xcode projects. So there's no direct build&run support, no jump to definition, no completion and no errors as you type, and no debugger.