-
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
Force global atrributes to be declared for every cluster in MatterIDL #24951
Force global atrributes to be declared for every cluster in MatterIDL #24951
Conversation
PR #24951: Size comparison from 11c0cdf to ea10d7e Full report (1 build for cc32xx)
|
PR #24951: Size comparison from 36735ed to a9d9294 Decreases (1 build for cc32xx)
Full report (1 build for cc32xx)
|
This does not seem to work - java read callback paths do not actually take into consideration that some things are just hard-coded and as a result we do not codegen the underlying types in CHIPReadCallbacks.h / CHIPReadCallbacks.cpp . Hardcoding into matter files makes more things available to the python codegen and results in build errors. Commenting out the event list was not sufficient. |
Updated PR: created a script to ensure all the mandatory attributes are enabled for all clusters. |
PR #24951: Size comparison from 36735ed to 61f3e1d Full report (2 builds for cc32xx, mbed)
|
…project-chip#24951) * Update IDL tempalte: force a fixed set of global attributes * Ran zap regen * Regen and fix some odd UFT8 wrong values * Comment out eventList from matter as ZAP global resposes does NOT yet seem to return this list. * Zap regen * Ensure acceptedcommandlist is available in ALL clusters * Zap regen * Add generated command list as well * Zap regen * Marking AttributeList as included for several clusters * Zap regen * Add EventList to all clusters * zap regen * Zap regen: re-enable event list attribute --------- Co-authored-by: Andrei Litvin <[email protected]>
Spect section
7.13 Global Elements
describes a set of elements that are mandatory for every cluster to have.Fixes #24947 for the matter IDL bits (although java may still depend on zap, where handling seems to need specialization)
It also turns out that both JAVA and PYTHON rely on zap templating to have global attributes enabled. As a result I updated controller_clusters.zap to enable mandatory attributes (a lot of event list adding, some adding/enabling for a few other clusters). This resulted in java and python generated code updates.