Developers
Downloads
Developer downloads should come from the project or supplier that owns the release.
What you’ll do
Developer downloads should come from the project or supplier that owns the release. A usable download record includes platform, architecture, ABI, version, checksum, licence, release notes and matching documentation.
Before you begin
Matching artefacts matters because a compiler, runtime image and simulator from different revisions can fail in ways that look like source-code defects.
Steps
1. Select
Choose the exact target and supported release rather than the most recently named file.
2. Verify
Check the source, checksum or signature, licence and release notes before installation.
3. Record
Capture the URL, version and configuration in the project’s build notes or dependency lockfile.
Check your result
Nightly and research builds may change without compatibility guarantees. Keep reproducible copies or pinned source revisions where licensing permits.
Record the architecture, platform, ABI, release, source revision and complete commands. A second developer should be able to reproduce the result.