-
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
[BUG] Build Python fails due to Zap Generation on Raspberry Pi (no ARM based version of zap-cli available) #24718
Comments
@oidebrett You should be able to do the pre-generation thing docs/code_generation.md describes, if the error is clear enough about which exact codegen bits you need.
Those libraries depend on some generated things, right now. Also note project-chip/zap#897 but that does not help you for the moment. |
And see also #24588 (comment) |
same problem |
I've created a PR to provide a fix for this. Allowing pregenerated files in python build #24752. Hopefully I followed the correct procedures for creating a PR. |
Just to add that I tested the modified build_python.sh script as follows: I pre-generated the files on a Ubuntu system that has zap-cli using I then transferred the zzz_pregenerated folder to the raspberry pi and ran That worked and built the python environment without the need for the zap-cli tool installed on the raspberry pi |
* checking that we can commit * checking that we can commit by deleting file that was added * modified build_python.sh to take argument to use pregenerated files as per issues - Build Python fails due to Zap Generation on Raspberry Pi (no ARM based version of zap-cli available) #24718 * Updated matter guide explaining how to use additional args for pregenerated code * fixed misspelling of Raspberry as picked up by reviewdog in CI tests * updated guide to state which things need to be pregenerated * added more information to the matter-repl.md file on pregeneration * fixed spelling mistakes such as pregeneration, pregenerated, pregen * patched with what the restyler is suggesting * Restyled by prettier-markdown --------- Co-authored-by: oidebrett <[email protected]> Co-authored-by: oidebrett <[email protected]> Co-authored-by: Restyled.io <[email protected]>
This can be resolved by building for arm64 eg. for raspberry pi A new argument has been added to the build_python.sh to allow the use of pre-generated files. e.g. scripts/build_python.sh -m platform -i separate -z ./zzz_pregenerated/ |
* checking that we can commit * checking that we can commit by deleting file that was added * modified build_python.sh to take argument to use pregenerated files as per issues - Build Python fails due to Zap Generation on Raspberry Pi (no ARM based version of zap-cli available) project-chip#24718 * Updated matter guide explaining how to use additional args for pregenerated code * fixed misspelling of Raspberry as picked up by reviewdog in CI tests * updated guide to state which things need to be pregenerated * added more information to the matter-repl.md file on pregeneration * fixed spelling mistakes such as pregeneration, pregenerated, pregen * patched with what the restyler is suggesting * Restyled by prettier-markdown --------- Co-authored-by: oidebrett <[email protected]> Co-authored-by: oidebrett <[email protected]> Co-authored-by: Restyled.io <[email protected]>
Reproduction steps
Result: FAILED TO EXECUTE ZAP GENERATION
Error suggests:
zap-cli
is in $PATH. Install from https://github.com/project-chip/zap/releasesThere is no compatible version of /zap/releases for ARM based architecture (i.e. Rasp Pi 4B+)
Can ZAP generation be skipped as we only require the python libraries so I can use chip-repl on the Rasp Pi? we would rather not have to download npm etc on the Rasp Pi just to get the ZAP-cli working. There was no previous dependency on zap-cli when running chip-repl previously.
Bug prevalence
When building for Python platform on Raspberry Pi
GitHub hash of the SDK that was being used
master
Platform
raspi
Platform Version(s)
master
Anything else?
No response
The text was updated successfully, but these errors were encountered: