Re: The double-folder thing ?
Re: The double-folder thing ?
- Subject: Re: The double-folder thing ?
- From: Fritz Anderson <email@hidden>
- Date: Sun, 04 Mar 2012 21:40:02 -0600
On 4 Mar 2012, at 8:00 PM, Erik Stainsby wrote:
> Every time I create a Project, I choose a parent directory and code generates something akin to this:
>
> <parent dir>
> ProjectName
> ProjectName
> ProjectName.xcodeproj
>
> I a case where I have a moderately complex application I have 40 projects related to each other. These extra folders add hours of seemingly unnecessary clicking around over the lifetime of the project. I'm a little ticked off and was wondering if anyone cares to explain why that top-level Project folder has to exist at all ?
When you create a project, you give it a name, and tell Xcode where you want to place it. That creates a folder with the project's name, with the project file inside it.
Because you selected a target type for the project (you had no choice), Xcode automatically created a target of the same name. Targets should keep their own directories, so it creates a target directory to hold your source, next to the project file. Your first target happens to have the same name as the project. If you were to add another target to the project, it would create a folder for that target, having the target's name.
Most people's moderately-complex applications have more than one target per project, so this is beneficial to them.
So you don't have a "double-folder" situation. You have:
<parent dir>
ProjectName
TargetName
ProjectName.xcodeproj
— F
_______________________________________________
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