Re: Xcode 4 Preference for Children Paths
Re: Xcode 4 Preference for Children Paths
- Subject: Re: Xcode 4 Preference for Children Paths
- From: Joar Wingfors <email@hidden>
- Date: Thu, 01 Mar 2012 19:32:56 -0800
Xcode 4 certainly intends to support the scenario that you outline. If there's something that isn't working, or that is difficult to achieve, please file a bug report:
<http://developer.apple.com/bugreporter/>
Joar
On 1 mar 2012, at 16:57, Brian Barnes wrote:
> This one took me a while to figure out, and it seems that Xcode prefers headers and sources to be children of the project file. Most of my projects (as they are cross platform) and most open source projects look like this:
>
> root
> --sources
> ----.c/.h files
> --projects
> ----xcode
> ------project file
> ----msvc (etc)
>
> Xcode 4 prefers this:
>
> root
> --xocde
> ----project file
> ----sources
> ------.c/.h files
>
> This second one is obviously bad as you don't want to duplicate all your sources files.
>
> What's happening is Xcode 4 likes to set paths to "relative to group", and *assumes* when importing that the group reflects the setup. Why older Xcode 3 projects work is the groups have a blank path, and then the "relative to group" acts like "relative to project." This was the key that took me a while to deduce.
>
> Not sure what the good fix for this would be, but I'm thinking that if you import files and do NOT select the "create groups/directories" or "move files", the files should default to "relative to project."
>
> [>] Brian
>
>
> _______________________________________________
> 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
_______________________________________________
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