Re: Xcode's Groups and Files View, SCM/Subversion and Non-Project Files
Re: Xcode's Groups and Files View, SCM/Subversion and Non-Project Files
- Subject: Re: Xcode's Groups and Files View, SCM/Subversion and Non-Project Files
- From: Christopher Hunt <email@hidden>
- Date: Sun, 9 Dec 2007 21:34:41 +1100
Hi again,
Following your suggestion:
However, you can change the project root. Brint up the Project Info window (via Project -> Edit Project Settings). Near the top is an entry called "Root", which is set to "<Project File Directory>". Click the "Choose" button in the same row, and you will be allowed to choose any directory that directly contains the project file:
Other Directory 1 (Can't be project root) +----Other Directory 2 (Can't be project root) Super Super Parent (Can be project root) +----Other Directory 3 (Can't be project root) +----Super Parent (Can be project root) +----Other Directory 4 (Can't be project root) +----Parent (Can be project root) +----Project File
I declare my project root has being the directory immediately above the Parent directory i.e. the Super Parent in your example. When I re-open the project I get:
Error: 155007 (Path is not a working copy directory) Description: '<snip>/Development/Titan Class Vision' is not a working copy Error: 2 (No such file or directory) Description: Can't open file '<snip>/Development/Titan Class Vision/.svn/entries': No such file or directory
My Super Parent directory isn't something that is hosted in svn... it is just a place that I have created to group my checked out modules and projects to (there are multiple Xcode projects below the Super Parent directory)... do you have any ideas on what to do in this situation?
Thanks again for your help.
Cheers, -C
On 06/12/2007, at 8:27 AM, Christopher Hunt wrote:
From an intuitive perspective, I expected Xcode handle SCM for all files under the Groups & Files view.
This is how Xcode 2 and earlier used to work.
Xcode 3 works a little differently, and it does so in part for the sake of efficiency.<snip>
So what I would suggest is that you put all the folders that you specify above inside a single parent directory, and change the project root for both project file 1 and project file 2 to be that parent directory.
Thank you so much for this tip.
While on the subject of SCM I get the feeling that the associated Xcode 3 documentation is a little out of date... the information you provided would certainly be useful in the doco. Should I file a request re. the documentation or is there an activity to update Xcode's SCM documentation already?
Cheers, -C
|
_______________________________________________
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