I discovered this while backfilling some specs for BetterConsole earlier this week. If you check out this commit and try to run the specs, you get an error message about duplicate symbols for CedarDoubleImpl, which also matches a class in the Cedar::Doubles C++ namespace. Pretty sure this is some additional fallout from making Cedar build as a static framework, but I haven't gone back and tried to bisect the problem. I have verified that Cedar is still buildable with carthage, and as a cocoapod and git submodule, so this should be a fairly innocuous change.
Cedar fully supports Carthage for iOS and OS X Some targets are renamed for clarity, lacking a more consistent convention Imports are reorganized and a few file types changed for more correct integration with C++ code Rakefile distinguishes between static and dynamic iOS frameworks Developers may want to delete and re-create auto-generated schemes after pulling
Untested with earlier versions of xcode. Apparently in Xcode 6.3 the TemplateInfo.plist has a version of the macros that xcode provides (e.g.:: ___FILENAMEBASE___) that are different from the contents of the template. The template contents use the *actual* file name, rather than what the user provides. This fix just captures the class the user typed as a variable, and then uses it in the template. I believe this should work on earlier versions of Xcode, but I haven't had the liberty to check yet. Fixes #324
This can occur by accidentally forgetting to create an `it` block before writing the assertion.