I have this scenario, in transition from Xcode 3.1 to 3.2:
-- Xcode project A.xcodeproj, with project folder A and SVN repository
-- A separate folder B containing additional source code used in
project A, with SVN repository B. (There's actually a project
B.xcodeproj in there, which existed solely to provide Xcode access to
repository B under 3.1. I'm pretty sure it's irrelevant to what's
going on here.)
-- So project A starts with just one root in 3.2, the project folder A.
-- I added a second root, folder B, so now there are 2 roots shown:
<Project File Directory>, ../B
-- The original project root was already set to the correct
repository, so I just need to set the ../B root to the matching
-- A.xcodeproj now shows as modified, so I commit changes.
What actually gets committed are a couple of user-specific files (such
as username.pbxuser). That means that other developers working on the
same project don't get their project roots updated, and have to do it
In other words, the project root configuration appears to be per-user,
not per-project. Is this a mistake, or is there some compelling reason
why it's being done this way?
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