Major Xcode irritation
Major Xcode irritation
- Subject: Major Xcode irritation
- From: Graham Cox <email@hidden>
- Date: Mon, 12 Aug 2013 21:31:23 +0200
Has anyone else run into this?
You open a system header from the SDK into XCode, and due to muscle-memory, absent-mindedness, reflex, lack of context or whatever, you hit cmd-S and save it over the old header (even if it hasn't actually been changed). XCode then refuses to build because the header file mod date no longer matches what was used when the precompiled headers were built.
OK, so let's restore that file - oops, no backup because I don't typically back up apps, and the SDK is embedded in the app. OK, download a new SDK from Apple - you can't, the SDK is part of the Xcode download which is 1.6 GB, not a swift download in most people's books. Rebuild the precompiled headers? Probably a fair option, but it's not obvious how one even does that these days, assuming it's still possible (help?).
Given that the SDK is embedded in the app, why on earth is it even allowed to overwrite a file there? Why do the permissions allow writing? Mysteries, mysteries... in the meantime I will have lost half a day's productivity just putting this stupid annoyance right.
/Gripe
If anyone could let me have a copy of NSEvent.h from the XCode 4.6.2 10.8 SDK with the mod date 10/4/2013 12:53AM that would save my sanity and my few remaining hairs - thanks!
--Graham
_______________________________________________
Cocoa-dev mailing list (email@hidden)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden