On Mar 4, 2011, at 09:31, Stephen O'Connor wrote:
> I've done this for reference folders (the blue ones) but want to do the same for XCode's flat hierarchy so I don't have to change all the paths of my include files, etc.
You're going to have to explain your problem a bit more clearly. What does a "flat hierarchy" have to do with it, exactly? You could use a group (yellow folder) for each of your source directories, and simply keep the groups expanded. That's not exactly flat, but pretty close. What does "change all the paths" mean? Originally you were asking about target membership. What paths are changing?
Or is this about reordering the files inside Xcode? You could use multiple groups for each directory, if you wished to rearrange the order of some sub-collections of files, and still just keep the groups expanded all the time.
Or is your point that you want to rearrange the order of the files inside the project so individual files from different groups (or reference folders) are adjacent to each other? (Like having the .m and .h files in different directories, but listing them side by side in Xcode.) I can't think of any way of doing this in Xcode without using groups or (fairly) absolute paths.
Am 2/28/11 3:47 PM, schrieb Stephen O'Connor:
> I'm working on a project where we have 2 different folders of common sourcecode that are imported into the project. When adding these to a project I don't copy the files (with the checkbox), but also don't create a reference folder (i.e. the source would then appear under a blue folder icon in the project) because I want a flat hierarchy. This works OK... up to a point.
> When I add these folders, the dialog will then ask me what target I want to set these files for. What I'd like to do is to say "This folder's contents - all of its files - should all have the same target(s). " That means, if I add/remove files from this folder (in Finder), the Xcode project will make itself aware of any changes to the contents of that folder (in Finder) when I build.
Basically, you're asking for build settings to be inferred from directory location. Xcode can't do that (AFAIK).
I'm trying to imagine a scenario where it's so onerous to set the target membership from within Xcode. You only do it once, and you can set it for multiple selected source files in one info window.
The only scenario I can think of where it might make sense is if you're working on a large project where another developer frequently gives you new source files to integrate into your project, so that it's really someone else's housekeeping you're doing.
If something like that is going on, I'd say your best choice is to start using source code management, and let them do their own housekeeping.
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