-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Fix ChipLog* calls in darwin-framework-tool itself to work right. #24195
Fix ChipLog* calls in darwin-framework-tool itself to work right. #24195
Conversation
darwin-framework-tool ends up linking in two copies of CHIPLogging, so the redirect we were setting up was only capturing ChipLog* calls that happened inside Matter.framework. The calls from darwin-framework-tool itself were getting dropped after being logged via os_log, and not showing up on stdout. Also includes a drive-by fix to stop building address-resolve-tool every time we build darwin-framework-tool. Fixes project-chip#24194
PR #24195: Size comparison from eafbaae to 8769084 Increases (6 builds for bl602, cc13x2_26x2, psoc6, qpg, telink)
Decreases (11 builds for bl702, cc13x2_26x2, esp32, nrfconnect, psoc6, telink)
Full report (53 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not a c# programmer, so please don't count this as a thorough review, but this looks correct, and I pulled the change, and the logs are now showing up AND in colour.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sigh.
Fast-tracking platform-specific fix with platform owner review. |
REVIEW NOTE: A whitespace-ignoring diff is a lot easier to review.
darwin-framework-tool ends up linking in two copies of CHIPLogging, so the redirect we were setting up was only capturing ChipLog* calls that happened inside Matter.framework. The calls from
darwin-framework-tool itself were getting dropped after being logged via os_log, and not showing up on stdout.
Also includes a drive-by fix to stop building address-resolve-tool every time we build darwin-framework-tool.
Fixes #24194