No description provided.
Let's do this after eliminating the project templates (which will heavily rely on the xcodeproj code), as it shouldn't churn so much by then.
Things like the PBXProject and framework definition in https://github.com/alloy/cocoapods/blob/master/lib/cocoapods/project_template.rb should first be moved into the Xcode::Project class.
The same applies to the code that configures the user’s project in installer.rb.
Done as of 7d64004, along with some super powers for PBXFileReference. Anything else obviously need doing before splitting off to a gem?
Cool. I think the majority of the project_template.rb code will have to move out to the Xcode gem, but no more small things like the above afaik.
I was a bit unimaginative this morning, so if you have an idea for a better name let me know, for now I have created a repo called xcode-builder, you have push access. Do you want me to do the initial moving out, or do you want to work on that?
I'll get to it sometime this week unless you beat me to it.
I would've called it "xcodeproj", so pick your favourite :-)
Works for me https://github.com/alloy/xcodeproj :)
Btw, I also want to move the workspace and xcconfig code out into the gem.
lol, my remark about those classes was unrelated to the gem name.
All set in the xcodeproj-gem branch once you've pushed the xcodeproj gem. (The one failing spec is, I think, yours.)
Great work! I’ll have a look at the failure tonight and go through the code one last time, then push.
I think we’ll have to rename the namespace module to reflect the name of the gem, i.e. Xcode => Xcodeproj
Merge branch 'xcodeproj-gem'. Closes #24.
Released 0.0.1 \o/