Skip to content

Conversation

fealebenpae
Copy link
Contributor

No description provided.

@fealebenpae fealebenpae self-assigned this Jan 22, 2016
@fealebenpae fealebenpae added this to the 1.6.0 milestone Jan 22, 2016
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@fealebenpae Does it make sense to add xcpretty here, too? This would reduce the build log in Xcode, that quite often makes it unresponsive.

Edit: On a second thought, that would make it pass twice through xcpretty and that doesn't work as nice.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd rather not do that, because Xcode relies on error messages being printed in the format they are in so that they can be picked up by the issues navigator. Besides, with GCC_WARN_INHIBIT_ALL_WARNINGS set, the endless drove of warnings will cease and the output should be smaller. Also, you can switch away from the output tab while the build is underway to mitigate the unresponsiveness problem.

@jasssonpet jasssonpet force-pushed the fealebenpae/xcpretty-logging branch from d7b0919 to e4fdd08 Compare January 28, 2016 15:37
jasssonpet added a commit that referenced this pull request Jan 28, 2016
@jasssonpet jasssonpet merged commit 517e28d into master Jan 28, 2016
@jasssonpet jasssonpet deleted the fealebenpae/xcpretty-logging branch January 28, 2016 15:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants