Backporting LogKit to Tiger proved to be a pain in the neck. Crossdevelopment is tedious and the macros-riddled code looks ugly. On the upside I fixed a few bugs and reorganized the projects. The current release SymbicLogKit 0.92 is tested under both Tiger (10.4.11) and Leopard and includes source for both the framework and examples.
To include SymbicLogKit in your own projects follow these steps:
- Add SymbicLogKit as a dependent project to your project.
- SymbicLogKit is built as a private framework so you will need to add a “Copy” stage to your target to place SymbicLogKit into a Frameworks subdirectory of your build product.
- Make your target dependent on the principal target of SymbicLogKit project.
- Now we need to tell the compiler where to look for the SymbicLogKit.framework since it isn’t available for inclusion in the project (it doesn’t exist yet). Modify Framework Search Paths setting in your build settings per configuration to point to the appropriate directory relative, for instance, to your project location e.g. $(PROJECT_DIR)/../SymbicLogKit/build/Release.
- Since the framework isn’t available for inclusion in our host project we will be weak-linking to it. Locate Other Linker Flags in you build settings and set it or augment it to include -weak_framework SymbicLogKit -framework SymbicLogKit
- You may want to uncheck Build Active Architecture Only build setting.
