Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New .gitignore structure overhaul #2057

Closed
6 tasks done
bilderbuchi opened this issue May 17, 2013 · 4 comments · Fixed by #2523
Closed
6 tasks done

New .gitignore structure overhaul #2057

bilderbuchi opened this issue May 17, 2013 · 4 comments · Fixed by #2523

Comments

@bilderbuchi
Copy link
Member

Some problems have cropped up since the last gitignore overhaul (#1107), we'll collect them here and I'll submit a PR.

See discussion in #1981.

  • ofxSynth and ofxThreadedImageLoader are missing in the official addon list.
  • some files are committed but match ignore rules (found with git ls-files -i --exclude-standard)
  • the one which could be optimized away would be the one in SerialTest.
  • apps/devApps/VboExample/bin/data/.gitignore could be renamed .gitkeep cause it's empty
  • see if it makes sense to simplify the gitignore collection in in apps/devApps/AdvancedImageLoading and /libs/openFrameworksCompiled/lib/*/
  • are the .elf & .hex files in serialTest necessary?
@bilderbuchi
Copy link
Member Author

So, the list of files which are in the repo erroneously is

$ git ls-files -i --exclude-standard
apps/devApps/projectGenerator/src/pugixmlLib/scripts/pugixml.xcodeproj/project.xcworkspace/contents.xcworkspacedata
apps/devApps/projectGenerator/src/pugixmlLib/scripts/pugixml.xcodeproj/project.xcworkspace/xcuserdata/molmol.xcuserdatad/UserInterfaceState.xcuserstate
apps/devApps/projectGenerator/src/pugixmlLib/scripts/pugixml.xcodeproj/project.xcworkspace/xcuserdata/molmol.xcuserdatad/WorkspaceSettings.xcsettings
apps/devApps/projectGenerator/src/pugixmlLib/scripts/pugixml.xcodeproj/xcuserdata/molmol.xcuserdatad/xcschemes/pugixml.xcscheme
apps/devApps/projectGenerator/src/pugixmlLib/scripts/pugixml.xcodeproj/xcuserdata/molmol.xcuserdatad/xcschemes/xcschememanagement.plist
scripts/ios/template/emptyExample.xcodeproj/project.xcworkspace/contents.xcworkspacedata
scripts/osx/template/emptyExample.xcodeproj/project.xcworkspace/contents.xcworkspacedata

There are a couple of things I need cleared up by XCode users. Calling @ofTheo @ofZach @julapy

1: it's clear that xcuserdata folders/files should be ignored. this is unproblematic as far as I can see. Correct? One exception: this pugixml.xcscheme seems to be a build scheme, but it's user-specific when it should be shared, which would move it into xcshareddata, resolving the problem. Correct? If so, could someone do that and commit it to the repo, so I can remove the xcuserdata folders?

2: *.xcworkspace is currently ignored according to this. Is this still correct? there seems to be disagreement in the SO community if thsi should be ignored or not: here, here, here. Do you know if I can safely remove those from the repo?

@kylemcdonald
Copy link
Contributor

  1. i think xcuserdata can be ignored competely, and i always ignore it in my .gitignore files. but i'm not positive about this, it would be good to have someone else chime in. i think sometimes my project files require users to select a certain build scheme, but i'm not sure.
  2. i looked through those SO responses, and my feeling is that if we are getting by ok without it, then it's fine to keep excluding it.

@ofTheo
Copy link
Member

ofTheo commented Aug 29, 2013

thanks!!

the only files we need to have for xcode are:

emptyExample.xcodeproj/project.pbxproj
emptyExample.xcodeproj/xcshareddata/xcschemes/emptyExample Debug.xcscheme
emptyExample.xcodeproj/xcshareddata/xcschemes/emptyExample Release.xcscheme

all other files inside of an xcodeproj folder can be removed

@bilderbuchi
Copy link
Member Author

awesome guys. I'll add this to the PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants