开发者

should I commit .xcodeproj file in SVN?

开发者 https://www.devze.com 2023-03-08 09:29 出处:网络
Should I commit the project file (.xcodeproj)? When I commit this file from one system and update it on a second system, the project gets corrupted and Xcode won\'t open it.

Should I commit the project file (.xcodeproj)? When I commit this file from one system and update it on a second system, the project gets corrupted and Xcode won't open it.

Is this expected behavior, or am I maybe doing something wrong? Here is my list of ignored files:

*.o,*.lo,*.la,*.al,.libs,*.so,*.so.[0-9]*,*.开发者_StackOverflowa,*.pyc,*.pyo,*.rej,*~,#*#,.#*,.*.swp,.DS_Store,*.pbxuser,*.perspective,*.perspectivev3,*.project.xcworkspace,*.xcuserdata,*.mode1v3,*.mode2v3,build/,build,/build/

Should I add something to this list? Should I forget the SVN and switch to GIT?

I am using Cornerstone as SVN client and using Xcode 3.2.5

Please help; I am stuck!


do commit and track it. specifically, there are a few bits in there which you want - the most important is project.pbxproj. it looks like you have already ignored the user-specific pieces (which is good).

problem is, it will conflict often in distributed environments. break your projects and/or their definitions into smaller pieces to avoid this risk. the project file is a text format - it will merge without issue in some cases.

i do not track these:

*.xcbkptlist
*.xcuserstate

but you'll want to track some of the scheme and workspace files, new in Xc4. again, don't bother tracking the user defined bits, unless you really like them to be tracked, and you are the only person committing.

another thing i recommend is to build to a central location which lies outside of your versioned source directories -- no build/ directories among the sources, even if they are ignored.


Should I commit the project file (.xcodeproj) ?

The project file is project.pbxproj, Yes, definitely. project.pbxproj is an important file for Xcode project.

  • iPhone Dev - How important is Project.pbxproj?


I had the same problem with Cornorstone this is because the project file itself may have conflicts. One reason for that was I added a file from first machine and I did not commit and on the second machine also another file was added. The first who commits does not have a problem but when the second commit a conflict will occur. And also if you changed any attribute in the project configuration. A solution is to open the project file that has the conflict with text editor and solve the conflicts.

0

精彩评论

暂无评论...
验证码 换一张
取 消

关注公众号