Ok, thanks for the information...
However, now I'm wondering how I'm supposed to know "When something
important changes in it"?
At this point, all I can do is do a diff and hope that I recognize
"something important."
Would it be safe to say that the user preference file does not, and
will
never have, anything kept in it that affects the way the project is
compiled? I don't care about stuff like build output or window
locations,
just options that could affect the compiled code...
Message: 13
Cc: email@hidden
From: David Ewing <email@hidden>
Subject: Re: What is stored in .pbxuser file?
Date: Fri, 9 Jan 2004 10:47:07 -0700
To: Ken Turkowski <email@hidden>
On Jan 8, 2004, at 11:06 PM, Ken Turkowski wrote:
On Jan 8, 2004, at 6:29 PM, Scott Tooker <email@hidden> wrote:
Per-user per-project settings are there (like a custom build
products
folder, custom executables, breakpoints, and bookmarks to name a
few).
We also store a bunch of window geometry info. We usually check them
in
periodically to archive them in CVS.
We've got a project that builds a compiler that generates C code from
a custom grammar. This C code is then linked in with human-generated
C
code to produce an executable. The only way we've been able to get
xcode to compile and debug it is to create a custom executable.
Obviously, this causes problems for new guys on the project, because
they then have to add a custom executable, which then gets stored in
the .pbxuser file instead of a file that can be checked in and used
by
everybody.
It there a way that we can teach xcode about an executable that is
constructed by a nonstandard means?
This is what the default.pbxuser file is for. Just copy another user's
.pbxuser file, and check it into the repository. New users will then
start out with those settings. Unfortunately, once a user has his own
.pbxuser file, changes to the default.pbxuser file don't get seen.
(There are cases where this sort of functionality would be nice, but
it
doesn't sound too critical for your case.)
Also note that even if everybody has their .pbxuser files checked in,
only their own personal file is used when opening a project. Other
files sitting on disk are ignored.
You could only check in the default.pbxuser file and use it as the
"master" one. When something important changes in it, you could have
people manually delete their own .pbxuser files.
Dave
Kevin Hoyt
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.