Skip to content
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.

Sign up for GitHub

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

Update documentation with zap supporting amd64 #28210

Merged
merged 2 commits into from
Jul 25, 2023
Merged

Update documentation with zap supporting amd64 #28210

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
82298be
ZAP supports arm64, doc this
andy31415 Jul 24, 2023
7dd79a6
Fix file name
andy31415 Jul 24, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 0 additions & 4 deletions docs/code_generation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -40,10 +40,6 @@ ZAP is generally installed as a third-party tool via CIPD during the build
environment bootstrap (see `scripts/setup/zap.json`), which makes `zap-cli`
available in `$PATH` when running in a build environment.

**NOTE**: zap packages are currently NOT available for `arm64` (like when
compiling on Raspberry PI.). In these cases one should check out zap from source
and set `$ZAP_DEVELOPMENT_PATH` as described below.

When matter scripts need to invoke `zap-cli` (for code generation) or `zap` (to
start the UI tool), they make use of the following environment variables to
figure out where the zap tool is located (in order of precedence):
Expand Down
4 changes: 2 additions & 2 deletions docs/guides/BUILDING.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -169,8 +169,8 @@ The ZAP tool scripting uses the following detection, in order of importance:
- Use this if you are developing ZAP locally and would like to run ZAP
with your changes.

- `$ZAP_INSTALL_PATH` to point to where `zap-linux.zip` or `zap-mac.zip` was
unpacked.
- `$ZAP_INSTALL_PATH` to point to where `zap-linux-x64.zip`,
`zap-linux-arm64.zip` or `zap-mac-x64.zip` was unpacked.

- This allows you to not need to place `zap` or `zap-cli` (or both) in
`$PATH`.
Expand Down