Skip to content

Commit 1bc65f7

Browse files
authored
Update ZAP installation description (#31825)
* Update ZAP installation description Remove arm64 since it is done automatically since #26636 * Improve explanations, describe the CIDP process * Improve link texts
1 parent a2c18ac commit 1bc65f7

File tree

1 file changed

+17
-12
lines changed

1 file changed

+17
-12
lines changed

docs/guides/BUILDING.md

+17-12
Original file line numberDiff line numberDiff line change
@@ -199,22 +199,27 @@ permanently, you need to make the following changes:
199199
200200
## Installing ZAP tool
201201
202-
`bootstrap.sh` will download a compatible ZAP tool version and set it up in
203-
`$PATH`. If you want to install or use a different version of the tool, you may
204-
download one from the ZAP project's
205-
[Releases](https://github.com/project-chip/zap/releases) page.
202+
For platforms defined in [`scripts/setup/zap.json`](/scripts/setup/zap.json),
203+
`bootstrap.sh` will download a compatible ZAP tool version from CIPD and set it
204+
up in `$PATH`.
206205
207-
### Linux ARM
206+
ZAP releases are copied to CIPD by an automated bot. You can check if a release
207+
was copied by looking at tags created for
208+
[ZAP CIPD Packages](https://chrome-infra-packages.appspot.com/p/fuchsia/third_party/zap)
209+
in various platforms.
208210
209-
Zap does not provide binary releases for arm. Rosetta solves this for Darwin,
210-
however for linux arm you will have to use a local ZAP, generally through
211-
setting `$ZAP_DEVELOPMENT_PATH` (see the section `Which zap to use` below).
211+
### Custom ZAP
212+
213+
If you want to install or use a different version of the tool, you may download
214+
one from the [ZAP releases](https://github.com/project-chip/zap/releases) or
215+
build it from source.
212216
213217
The file `scripts/setup/zap.json` contains the version that CIPD would download,
214-
so you can download a compatible version from the zap project
215-
[Releases](https://github.com/project-chip/zap/releases). To checkout as source
216-
code the corresponding tag should exist in the zap
217-
[repository tags](https://github.com/project-chip/zap/tags) list.
218+
so you can refer to it to find a compatible version. The version is also
219+
maintained at [`scripts/setup/zap.version`](/scripts/setup/zap.version).
220+
221+
To check out as source code, the corresponding tag should exist in the
222+
[ZAP repository tags](https://github.com/project-chip/zap/tags) list.
218223
219224
Example commands:
220225

0 commit comments

Comments
 (0)