I set that to 10.11 for El Capitan, and rebuilt my app. Up popped choices ranging from 10.6 (back in 2009) to the latest 10.12. From among the scores of different switches and options, I found the one which claimed to set the macOS deployment target. My mistake was to assume that I could make this new backward-compatible version by changing a single setting in Apple’s Xcode development environment. As much of it works by running shell commands, and I developed it partly as an example of how to script in Swift 3, it looked fine. It took me a little while to check that my code didn’t do anything specific to Sierra. ![]() It wasn’t a particularly demanding request: someone wanted a version of my little security tool LockRattler which runs on El Capitan, rather than Sierra.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |