> On Jul 20, 2015, at 11:48 PM, Rick Mann <[email protected]> wrote: > > It takes several minutes for OS X to verify Xcode on a 2.8 GHz MacBook Pro. > The progress bar fills in under a minute, but then it sits there, fans > screaming, for another while.
Not surprising, since it’s reading from disk and computing cryptographic digests of several gigabytes of data. > I finally decided to forego the warning about being unable to verify the app, > since 7b2 is now crashing 100% when I open my project, and I need to see if > b3 fixes this. So I went to Sys Prefs to "Open Anyway," and nothing happened. > So set permissions to allow opening any app from anywhere. Relaunched Xcode, > and it verified again. This really belongs in a bug report filed with Apple, not on this list. No offense, but (a) you’re the only one seeing this problem, so the discussion isn’t helping anyone else, and (b) no one’s been able to provide any help; this definitely seems like some kind of issue with Gatekeeper on your system, and only Apple engineers have the inside access to debug it. > Why is Xcode so damn big? Well, let’s open up the bundle and check “Calculate all sizes”… 90% of it is the Developer folder (the one that used to be at /Developer before Xcode 4.) Of that, the vast majority is the iPhone simulator (3GB) and Watch simulator (1.6GB). Not surprising: those are two entire operating systems. Then there’s 750MB of documentation, 650MB of toolchain (all the compilers and other contents of /usr/bin…) —Jens
_______________________________________________ Do not post admin requests to the list. They will be ignored. Xcode-users mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/xcode-users/archive%40mail-archive.com This email sent to [email protected]
