Uninstall Mac apps with every file they leave behind, and see why each belongs. Free up space, fine-tune macOS, and set up Terminal.
Swift cache-cleanercleanerclideveloper-toolsdisk-cleanupdisk-spaceduplicate-finderhomebrewliquid-glassmac-cleanermacosmacos-appmacos-golden-gatemacos-tahoemacos-tweaksswiftswiftuiterminal-themesuninstalluninstaller
Say that a self-built app and helper pair up in Debug
Țugui Dragoșea8cd8f680c3
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.mdindex c987f87a..896629ed 100644--- a/CONTRIBUTING.md+++ b/CONTRIBUTING.md@@ -31,9 +31,10 @@ to Terminal.- A team to sign with, even a free one. The project names its maintainer's team, so build with yours: add`DEVELOPMENT_TEAM=YOUR_TEAM_ID` to the `xcodebuild` command, or choose your team for the targets under Signing &Capabilities in Xcode and leave that change out of your commits. The helper accepts only an app signed by the- same team as itself, so the app and the helper you build work together. launchd starts the helper only as the- team named in `Support/com.tuguidragos.Peel.Helper.plist` (`SpawnConstraint`), so to install the helper you- build, put your team there as well, again outside your commits. The package's tests need no signing.+ same team as itself, so the app and the helper you build in Debug work together; a Release helper accepts only a+ Developer ID build that can't be debugged. launchd starts the helper only as the team named in+ `Support/com.tuguidragos.Peel.Helper.plist` (`SpawnConstraint`), so to install the helper you build, put your+ team there as well, again outside your commits. The package's tests need no signing.- Nothing else. The only dependency is Apple's swift-argument-parser, which Xcode fetches.- A Release build needs `ENABLE_POINTER_AUTHENTICATION=YES` and `MACOSX_DEPLOYMENT_TARGET=26.0` on the`xcodebuild` command line, since only the command line reaches the Swift packages: every program imports