I developed a static library that I would like to share between Xcode projects. I read some data to learn how to include this library in a binary dependency so that it works both on the device and on the simulator, and this led to several manual steps that I would now like to automate. In general, I would like to be able to release new versions of my library and have a simple upgrade process for any project using the old version. Currently, this process consists of deleting and / or copying new binary files to their original location, removing copying new header files. The initial installation consists of the same two steps as the additional project / target configuration for setting conditional linker flags based on the target SDK.Is it possible to automate this? I mean, I know that I can do something like writing Applescript to do a heavy lift, but how? Has anyone ever automated xcode build settings through applescript? How can I call Xcode through Applescript? Are there any other alternatives? Is there a better way to support binary level dependencies?
Update
I am looking to maintain a dependency on the binary level, where project A depends on the static library created by project B. Something similar to a structure that can easily be included in an iPhone Xcode project. After creating “B,” I want something that you can practically flip and design, including A. While I learn about all the procedures involved in using this dependency, I’m looking for some solutions to soften all the rough edges.
Cliff source
share