-
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
Matter zap cleanup #21713
Matter zap cleanup #21713
Conversation
47a8e60
to
51279c7
Compare
PR #21713: Size comparison from 0888818 to 51279c7 Decreases (1 build for bl602)
Full report (12 builds for bl602, cyw30739, linux, mbed, nrfconnect, telink)
|
PR #21713: Size comparison from 0888818 to 71f38b2 Increases above 0.2%:
Increases (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
Decreases (10 builds for cc13x2_26x2, p6)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, 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.
Is the change to submodule silabs/matter_support wanted? I don't see the reason for it
@jmartinez-silabs : It's not. I'll remove that change from the PR. Well, I have to rebase the whole thing anyway, so I'll just rebase that change out of existence. @jmartinez-silabs : taken care of. The new rebased branch doesn't have a change to silabe/matter_support. |
0. Use the common helper aliases in the template json files. 1. Update templates.json with correct reference. 2. Update another template. 3. Add resources to the templates files, so that helpers can access the yaml stuff. 4. Fix wrong paths in templates.json
c83c5f6
to
f9ae43d
Compare
PR #21713: Size comparison from 1c613ad to f9ae43d Increases (2 builds for bl602, cyw30739)
Decreases (1 build for telink)
Full report (18 builds for bl602, cyw30739, k32w, linux, mbed, nrfconnect, p6, telink)
|
PR #21713: Size comparison from 1c613ad to 42356ae Increases (4 builds for bl602, cyw30739, telink)
Full report (21 builds for bl602, cc13x2_26x2, cyw30739, k32w, linux, mbed, nrfconnect, telink)
|
PR #21713: Size comparison from 1c613ad to 1c93a9b Increases (5 builds for bl602, cc13x2_26x2, cyw30739, telink)
Decreases (1 build for cc13x2_26x2)
Full report (43 builds for bl602, cc13x2_26x2, cyw30739, efr32, esp32, k32w, linux, mbed, nrfconnect, p6, telink)
|
* Add the sdk.json for zap regeneration. * Rework the helper infrastructure to support aliases and categories. 0. Use the common helper aliases in the template json files. 1. Update templates.json with correct reference. 2. Update another template. 3. Add resources to the templates files, so that helpers can access the yaml stuff. 4. Fix wrong paths in templates.json * Use ZAP_PATH to run zap from other location than third_party/zap. * Convert the tests to JSON files. * Remove all the duplicated and unneeded js code. * Keep tests in sync with the changes on master. * Update zap submodule. * Add the updates from the mainline. * Restyled by whitespace * Restyled by prettier-json * Remove a manual test. Co-authored-by: Restyled.io <[email protected]>
Problem
ZAP source dependency was detrimental to end-customer experience, because every Matter end user had to set themselves up as a ZAP developer: right versions of node, right versions of some shared libraries, etc. The binary build of zap could not be used, because the JS extensions on the Matter SDK reached back into the zap repo looking for source code, which does not exist in a binary build.
Change overview
Testing
Follow-up
This work opens up the ability to run zap differently. So there will be follow-up work afterwards: