• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag
 

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: any reason to source control the build dir (index) contents?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: any reason to source control the build dir (index) contents?


  • Subject: Re: any reason to source control the build dir (index) contents?
  • From: Alexander von Below <email@hidden>
  • Date: Fri, 24 Oct 2008 17:35:28 +0200

Especially in version control, I would always exclude them

Including them looks like a hazard in multi-developer environments to me.

Alex

Am 24.10.2008 um 17:28 schrieb Martin Redington:

In my projects, I usually exclude the build directory and the
*.xcodeproj/<username>.* files from source control.

I also usually set up a clean.sh script, that blows away the build
directories completely - historically (with Xcode 2.0 for example) I
very very occasionally saw issues where a normal clean wouldn't
somehow seem not to have removed all the previous state.

I usually just Clean All from the gui, but every once in a while I'll
blow build away just for good measure (my projects are all pretty
small, or tens of thousands of loc at most, so this isn't especially
painful).

I've been creating a lot of new projects recently (this is with Xcode
3.1, but presumably other versions as well) and noticed that the
default templates (or at least the "iPhone View Based app" template)
creates a build directory off the bat, with a lot of indexing
information. e.g.

ls -1 build/Gravity.build/Gravity.pbxindex/

categories.pbxbtree
cdecls.pbxbtree
decls.pbxbtree
files.pbxbtree
imports.pbxbtree
pbxindex.header
protocols.pbxbtree
refs.pbxbtree
strings.pbxstrings/
subclasses.pbxbtree
symbols0.pbxsymbols

I'd hazard a guess that these are indexes for code completion etc.

Is there any reason, apart from a very minor speed bump in my usual
case, to source control these, or to not blow them away?

Is there any point at which you should consider not blowing them away
(e.g. for projects beyond a certain size)?




-- http://www.mildmanneredindustries.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

_______________________________________________ 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
References: 
 >any reason to source control the build dir (index) contents? (From: "Martin Redington" <email@hidden>)

  • Prev by Date: any reason to source control the build dir (index) contents?
  • Next by Date: CodeSign Warning when building static lib target for iPhone on XCode 3.1
  • Previous by thread: any reason to source control the build dir (index) contents?
  • Next by thread: Re: any reason to source control the build dir (index) contents?
  • Index(es):
    • Date
    • Thread