project roots in 3.2
project roots in 3.2
- Subject: project roots in 3.2
- From: Steve Mills <email@hidden>
- Date: Thu, 22 Oct 2009 16:43:58 -0500
When I first started using 3.2, I set up our projects to have multiple
project roots, one for each folder that we get source, headers, and
other projects from (there are many). A couple times I checked in a
bunch of changes via the SCM Results window (selected checked out
files and submitted them), and noticed that instead of one changelist
being added to our Perforce depot, multiple were added. I just now
figured out that it's adding one changelist per root that has a file
is checked out in it. This is annoying and wrong. Is there any way to
make it NOT do that?
If not, I'll go back to having 1 root at the top level of the depot
(well, top of the branch the project is in). If I do that, is there a
way to tell it to exclude certain folders or files? Like the way it
shows all the .o files from my build dir. That's useless and junks up
the SCM Results window. I'd like to exclude that from the source roots.
Steve Mills
Drummer, Mac geek
http://sjmills5.home.mchsi.com/
_______________________________________________
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