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

Support comments attribute in all build phases, groups and targets. #51

Merged
merged 2 commits into from
Feb 9, 2013

Conversation

drodriguez
Copy link
Contributor

Xcode 2 and 3 used to have a comments attribute almost everywhere. I have
found instances of comments in:

  • PBXShellScriptBuildPhase
  • PBXCopyFilesBuildPhase
  • PBXNativeTarget
  • PBXApplicationTarget
  • PBXLibraryTarget
  • PBXAggregateTarget
  • PBXGroup

Seems that Xcode 4 doesn't remove those comments, so supporting them is nice for people with old projects being converted to CocoaPods.

A search in Google for "filetype:pbxproj comments" gives you some of this results.

Fixes CocoaPods/CocoaPods#696

Xcode 2 and 3 used to have a comments attribute almost everywhere. I have
found instances of comments in:
- PBXShellScriptBuildPhase
- PBXCopyFilesBuildPhase
- PBXNativeTarget
- PBXApplicationTarget
- PBXLibraryTarget
- PBXAggregateTarget
- PBXGroup
I should actually write and *build* the test before commiting.
@fabiopelosin
Copy link
Member

Looks reasonable. Would you like push access to directly commit patches you feel confident about?

fabiopelosin added a commit that referenced this pull request Feb 9, 2013
Support comments attribute in all build phases, groups and targets.
@fabiopelosin fabiopelosin merged commit 750e41a into CocoaPods:master Feb 9, 2013
@drodriguez
Copy link
Contributor Author

Thanks Fabio, already have push access. The confidence is what’s I’m not sure about :D

@drodriguez drodriguez deleted the legacy-xcode3-attributes branch February 9, 2013 16:29
@fabiopelosin
Copy link
Member

Thanks Fabio, already have push access.

Oh, yes... I thought I've checked.

The confidence is what’s I’m not sure about :D

Yes if in doubt opening a pull is much better. Thanks for the contribution!

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

Successfully merging this pull request may close these issues.

*pod install* fails when encountering unrecognized property in project.pbxproj
2 participants