-
Notifications
You must be signed in to change notification settings - Fork 140
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade instructions missing #178
Comments
Totally agree that running it with no args should fail earlier with more helpful output. rake install is still the correct way to update your Xcode environment, but it looks like you have discovered an issue that the old OSX template was renamed to OS X, and the old one was not cleaned up properly. This should make it into the backlog as a bug. |
Thanks for reporting these issues. I have added the following to Cedar's backlog, and they should be addressed in the next release. https://www.pivotaltracker.com/story/show/64936304 BTW, if you want to upgrade manually as you described, you can run |
Thanks for the clarification! I wonder which role Alcatraz is playing. Building seems to work, but I don't know what'll be missing.
After I ran the install.sh script again, creating a Bundle target in a new Xcode project results in an empty |
Alcatraz isn't related to Cedar, and Cedar doesn't use it, either. AFAIK they don't interfere with each other. The error you're seeing in the logs is Xcode complaining that the Alcatraz plugin doesn't claim to be compatible with that version of Xcode and as such, it won't load that plugin. With regards to the empty Cedar.framework file, that's quite unusual. Would you be able to examine the |
Ok. Didn't know this was a problem on my side, sorry.
I wouldn't know what to expect since the folder duplications don't make sense for me. Can you tell me what to look for more specifically? These are the subfolders:
And this is the output of a dir listing (
|
Sorry for taking so long on this. I took a good look at the OS X templates today, and found the install script had an error which wasn't copying the framework correctly. I've committed 15e5a7c to master which should fix this. |
The Rakefile update states that upgrading is as simple as:
Now I only have to find out what
path_to_framework
should be to do this on my own.*
Cedar-iOS.framework
resides in~/Library/Developer/Xcode/Templates/Project Templates/Cedar/iOS Cedar Spec Suite.xctemplate/
, but I'm developing a Cocoa OS X app.OSX Cedar Spec Suite.xctemplate
has a similar structure but isn't a.framework
file.xctemplate
is calledOS X Cedar Spec Suite.xctemplate
(not the additional space before the 'X') -- is this due to me running the install script for the upgrade, and did the script omit deleting old files?Please provide some additional info. Best way I could come up with is to create a new project, add Cedar target, and copy the resulting
.framework
file over to my existing projects.Here's what my shell says when I run
rake upgrade
. Seemingly, no path is missing (it's inherited by other tasks?).The text was updated successfully, but these errors were encountered: