| Summary: | [Mac] xcodebuild color output is suppressed when using make | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | mitz | ||||
| Component: | Tools / Tests | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | simon.fraser | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
mitz
2014-01-11 10:13:15 PST
Created attachment 220936 [details]
Pass COLOR_DIAGNOSTICS=YES to xcodebuild
Fixed (to the extent possible) in <http://trac.webkit.org/r161772>. This caused a "make d" in Source/WebCore to do a full rebuild because its environment has COLOR_DIAGNOSTICS=NO (In reply to comment #3) > This caused a "make d" in Source/WebCore to do a full rebuild because its environment has COLOR_DIAGNOSTICS=NO Is this something specific to WebCore? When I try this in Source/WTF I see COLOR_DIAGNOSTICS being set to YES when using make and to NO when building in the Xcode IDE, but alternating between the two doesn’t cause any files to recompile. I’m using Xcode 5.1. This may depend on the Xcode version. I've only noticed this rebuilding issue fairly recently. (In reply to comment #5) > This may depend on the Xcode version. I've only noticed this rebuilding issue fairly recently. Just using xcodebuild from the command line (without piping through a filter) results in COLOR_DIAGNOSTICS being set to YES, whereas building from the IDE sets it to NO. If this difference alone causes some version of Xcode to rebuild everything, then it’s an issue with global impact, not affecting only WebKit. |