Re: 4.3 question and old Developer folder
Re: 4.3 question and old Developer folder
- Subject: Re: 4.3 question and old Developer folder
- From: "Rick C." <email@hidden>
- Date: Sun, 19 Feb 2012 15:21:07 +0800
Thank you all for the detailed replies. This is very helpful and I'll go grab a copy of those Release Notes that we're mentioned. Much appreciated,
rc
On Feb 19, 2012, at 2:53 PM, Joar Wingfors wrote:
> Hi guys,
>
> Please find my comments inline. I'm replying to both Rick and Fritz at the same time, hope it's clear when I'm doing which.
>
>
> On 18 feb 2012, at 19:45, Fritz Anderson wrote:
>
>> On 18 Feb 2012, at 8:26 PM, Rick C. wrote:
>>
>>> So when I launch 4.3 for the first time it asks me to remove the old Developer folder which I did not do since I have other important information there.
>>
>> Putting anything non-Apple in /Developer has always been a bad idea. Updates had the right to destroy anything in it, and you might have wanted to do a clean reinstall to quash bugs. Documentation and auxiliary files are kept in /Library or ~/Library to preserve user state against radical changes to the developer directory. But sometimes third-party frameworks force you to do it. Now that the Developer directory is inside Xcode.app/Contents, maybe people will get the message.
>
>
> Agreed. It's never been our intention, or a good idea, that you should put anything in your developer folder.
>
>
>>> I understand that in 4.3 I need to install everything from the Downloads pref.
>>
>> Documentation and legacy iOS development tools, yes. Don't quote me, but I believe the one goes into /Library/Developer/Documentation, and the other into Xcode.app.
>
>
> Once you have Xcode installed, that should be all you need for basic Mac and iOS development - No need to install anything else. If you want to be able to do traditional command line unix development then you'd probably opt to also install the separate Command Line Tools package, which you can get to from the Downloads preferences pane in Xcode (where you also find the other things that Fritz mentioned above). I'm not sure that I understand the "need to install everything" comment, but perhaps I'm just reading it wrong.
>
>
>>> Am I also to understand that the Developer folder is no longer needed at all? So where does 4.3 store all of the tools, command line stuff, etc?
>>
>> Inside the app package. The command-line stuff is no less accessible: It's still at least linked to /usr/bin, it all has man pages; and I just checked SetFile (which you had to access through a $PATH into /Developer), and it's been moved to /usr/bin.
>
>
> Correct. If you're not interested to keep earlier versions of Xcode around, you can (perhaps should) delete your old developer folder(s).
>
> Xcode itself has not needed to have command line tools installed into /usr in a long long time, but instead relied on its own copies of these tools (they used to live in the developer folder, and now inside of Xcode.app). Starting with Xcode 4.3 we now no longer install command line tools into /usr per default. If you need them, you can get them as I described in the paragraph above.
>
>
>>> I don't want to keep two installs on my machine, is there a way then to just uninstall the Xcode files from the Developer folder but keep the other info the way it used to work? I always kept my frameworks, etc. there and I don't just want to trash the whole folder.
>>
>> I'm speaking a priori here, so the Xcode team may have done something that delights the customer and proves me wrong. However:
>>
>> /Developer no longer has a privileged role in the build system, so there's no point in keeping anything in a path that happens to be rooted there. You'd have to manually add /Developer to framework search paths the same as if it were any other directory. If your frameworks are intended to be a system-wide facility, move them to /Library — they'd be in a default search path. If they're just a development resource, there's no reason they can't be somewhere in your home directory (or your external drive, or /Users/Shared, or whatever).
>
>
> On the whole I'd agree with Fritz here. In terms of where you keep custom frameworks, the developer folder was never a good location to begin with, and it also didn't come with any special behavior. You'd be better off moving your custom frameworks elsewhere. Not sure what else you used to keep there, but I bet most of it would be better off moving to your home directory.
>
> Fritz: How would you like to be delighted here? What is the problem that you'd like for us to resolve?
>
>
>>> PS - I also could find no release notes except the "What's new" section in the App Store???
>>
>> I wasn't going to answer this (it's not even a question), but you used _three_ question marks, and that means I have to. [I don't smiley.]
>>
>> You're right. Given the big change in how applications and directories are stored — there was real value in being able to examine the /Developer directory — there ought to be detailed release notes to explain how to make the transition. This is elementary. For a real blast from 2007, Apple might even have admitted to fixing bugs, so we could stop straining to avoid now-gone crashers.
>>
>> Help > Release Notes should reveal the 4.3 release notes, but the notes stop two releases back, at 4.2.0. Also, the document you get by selecting Help > Release Notes tells you that if you _really_ want the release notes, "visit the Mac or iOS Dev Center and go to the Xcode 4 download section." The preferred method of distribution being the App Store, there is no such section. The release notes would have accounted for that if someone had updated them for Xcode 4.3. Possibly, if you follow the other-downloads link, and fetch the Xcode 4.3 .dmg, you'll find notes in there, but I have a life.
>>
>> This does not delight the customer.
>
>
>
> We fixed thousands upon thousands of issues in Xcode 4.3. While we could list some or all of them, that has - as you probably know - not been our tradition. If you feel that we should be better about getting back to you when issues that you've filed bug reports about have been fixed, please let us know. The best way to make sure that your feedback gets routed to the right place is to file a bug report, and that's true in this case as well.
>
> If you have any other comments on why you feel that you'd need to rummage through the developer directory to figure something out, and what we could do to make that task either unnecessary or easier in the new world where everything is relocated to inside of Xcode.app, again - please let us know.
>
>
> Joar
>
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden