From 511837113040f6cca4fd23016b4c0fdda183140b Mon Sep 17 00:00:00 2001 From: Andrei Litvin Date: Mon, 24 Jul 2023 21:00:13 -0400 Subject: [PATCH] Update documentation with zap supporting amd64 (#28210) * ZAP supports arm64, doc this * Fix file name --- docs/code_generation.md | 4 ---- docs/guides/BUILDING.md | 4 ++-- 2 files changed, 2 insertions(+), 6 deletions(-) diff --git a/docs/code_generation.md b/docs/code_generation.md index 318cfedd359954..e12bf40f100cff 100644 --- a/docs/code_generation.md +++ b/docs/code_generation.md @@ -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): diff --git a/docs/guides/BUILDING.md b/docs/guides/BUILDING.md index 26ff8d59485e13..359b35e3d6b2d4 100644 --- a/docs/guides/BUILDING.md +++ b/docs/guides/BUILDING.md @@ -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`.