danielctull
Dropping project files causes problems for users DCTCoreData via static lib
Greetings. Had DCTCoreData nicely integrated into a project as a static lib dependency using an Xcode workspace. The latest changes drop the project files.
So I've been flipping back and forth about whether to use static libs. My current stance is that they are just way too much hassle.
The structure of the branches has changed, so that the master branch is effectively the same as what production used to be.
There is a demo branch with the demo project, this pulls in the DCTCoreData library files from the master branch as a submodule. I'd imagine you should be able to add your static library to that project to build, making sure to recursively add submodules.
Does this help at all?
I used to not bother with static lib dependencies but Xcode workspaces make things much better. Think I'll hold off on merging though for now. Thanks.