OCAUtilities is a set of classes that perform useful functions.
Most are implemented as category extensions.
Coming - add instructions to use as a Git Subproject
- Add the libOCAUtilities.a file to your target(s).
- Add the .h file using the new file. Be sure to Check the “Copy items into destination groups’s folder” checkbox.
Coming - add instructions to integrate
To keep up to date, issue
git pull either from the terminal or within Xcode. If you’ve included OCAUtilities as a SubProject and added it as a dependency of your main application, it will rebuild automatically.
Integrating with Xcode
Coming - add instructions to add build dependency.
Have problems? This is what you can do to troubleshoot:
Minimum system requirements
- Xcode 5 or greater for compiling
- iOS 7 or greater
OCAUtilities is licensed under MIT license.
Building the library is a bit complex. Summary below, details here.
- Build for device.
- Right-click the .a Product and Show In Finder.
- Rename to indicate its the device build - e.g., libOCAUtilities_device.a
- Repeat 1-3 building for simulator and rename the product libOCAUtilities_simulator.a
- Put the two .a files into the same folder
- In terminal, navigate to the folder containing the libraries and run the following command: lipo -create libOCAUtilitiesdevice.a libOCAUtilitiessimulator.a -output libOCAUtilities.a
- Copy OCAUtilities.h into the same folder.
- This folder now contains the static library and the associated .h file
- Copy the folder to the O'Mara Consulting Associates Library container.
- I use AppleDoc from GentleBtyes to create Apple-style API documentation from comments.
- Refer to the AppleDoc page for details.
- To simplify useage as a library, all the header information is embedded in OCAUtilities.h rather than distributed to .h files corresponding to their .m counterparts.
- To build the documentation just choose the GenDocumentation build option.