Re: Custom Executable, user file versus project file
Re: Custom Executable, user file versus project file
- Subject: Re: Custom Executable, user file versus project file
- From: Michael Rawdon <email@hidden>
- Date: Wed, 7 Dec 2005 10:15:58 -0800
Hi Wil -
On Dec 7, 2005, at 7:17 AM, William Turner wrote: I have a project which has several developers and is SCM managed in Subversion.
I recently added a custom executable to speed up testing. It seems that the custom executable information is stored in the user file (Project.xcodeproj/<username>.pbxuser) rather than in the project file. So, when I committed my changes, I found that none of the other developers got the custom executable, but had to add it themselves. Since we have roughly 25 more projects of this kind (all plugins), it would be nice if there was a way around this.
Suggestions/corrections?
Unfortunately there's only a limited way around this:
If you copy your <yourname>.pbxuser file to default.pbxuser , then anyone who opens the project and does not already have their own .pbxuser file will have the default.pbxuser file copied into place as their own. (You may want to trim down the pbxuser file in a text editor down to just what you want to make commonly available before making it the default file. It's not too hard, but does require learning a little about the project and user file structure.)
However, users which already have their own pbxuser file will not be able to take advantage of this.
Someday we (or at least I :-) would like to provide both per-project and per-project-per-user custom executables, but clearly we're not there yet, and presently only have the latter.
--
Michael Rawdon Apple Computer, Cupertino CA
Xcode Developer 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