That's where we are going. The reason we went with shipping a binary .framework is because of Xcode 4 and it's limitations regarding project template definitions (not supported nor documented) - there was no way to link to a subproject. With cli tooling we have more control.
On Thu, May 10, 2012 at 4:06 PM, Patrick Mueller <[email protected]> wrote: > On Thu, May 10, 2012 at 5:32 PM, Shazron <[email protected]> wrote: > >> D'oh - we can't have dual support of course, since this is compile >> time and we ship a built binary for the framework. We'll have to turn >> it on, and require ARC. The problem is, all the plugins will need to >> upgrade as well. >> > > We should stop shipping a framework, and start shipping the source files in > the framework, once we have the command line tooling working well. Goes > along with not shipping an Xcode template, but creating the Xcode files > with the command line tooling. > > -- > Patrick Mueller > http://muellerware.org
