From 0e620696b42a50f141049faffef7a8c66b6ffa14 Mon Sep 17 00:00:00 2001 From: Graham Hall Date: Mon, 1 Dec 2025 13:14:18 -0500 Subject: [PATCH] fix typo --- .../blog/2025/building-a-mac-app-without-xcode-part-1.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/blog/2025/building-a-mac-app-without-xcode-part-1.md b/src/content/blog/2025/building-a-mac-app-without-xcode-part-1.md index 09c5241..65e2761 100644 --- a/src/content/blog/2025/building-a-mac-app-without-xcode-part-1.md +++ b/src/content/blog/2025/building-a-mac-app-without-xcode-part-1.md @@ -10,7 +10,7 @@ So, I decided to try migrating my app, [AutoDock](https://github.com/ghall89/Aut 1. Whichever editor I use, I need access to the Swift language server. 2. The build process should produce a functional MacOS application bundle as a universal binary (for both Intel and ARM CPUs). -3. I should be able to use regular security features available to apps build with Xcode, like sandboxing, hardened runtime, etc. +3. I should be able to use regular security features available to apps built with Xcode, like sandboxing, hardened runtime, etc. 4. The final binary should be signed with my developer certificate. To prevent this blog post from being far too long, I’ve decided to split it up into multiple parts. This first part will focus on LSP support, and building the application bundle.