Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Fix the setting for SKIP_INSTALL in Xcode project (#4195)
The official docs don't say a lot about `SKIP_INSTALL`, but I missed the mark during the #4172 PR, where the ideal setup is NO for debug, YES for release. I spent a lot of time figuring this out a couple of years back but the other day I completely forgot about it 🤦 <img width="1128" alt="image" src="https://github.com/user-attachments/assets/4256ec42-00c2-4de2-a622-9a151b849781"> <img width="747" alt="image" src="https://github.com/user-attachments/assets/c8cdf454-0558-489b-bb24-b3006a4ebacb"> Here's ChatGPT's far better explanation than Apple's: ``` • Debug Configuration: • SKIP_INSTALL = YES • During development, you typically don’t need to install (or include) the product (e.g., .framework, .app) in the final build output. The focus is on quick builds, so setting SKIP_INSTALL = YES can help speed up the process by skipping unnecessary steps. • Release Configuration: • SKIP_INSTALL = NO • In the Release configuration, you usually want to include everything in the final build output. This is particularly important when archiving for distribution or creating .xcframeworks, as you need the final product to be available in the archive. Example Scenario If you are building a framework that is used by other targets in your project: • Debug Configuration: • Set SKIP_INSTALL = YES so that intermediate builds are faster, and the framework isn’t unnecessarily copied to the install location. • Release Configuration: • Set SKIP_INSTALL = NO so that when you archive the framework, it is included in the final archive, making it available for distribution or further use. ```
- Loading branch information