| Chong Gu | 70ad2c9 | 2021-12-03 00:55:44 | [diff] [blame] | 1 | # Fuchsia platform versioning |
| 2 | |
| 3 | When building for Fuchsia, the binaries are built against a target API level, |
| 4 | which is set via `fuchsia_target_api_level` in the [`.gn` file](../../.gn). This |
| 5 | information becomes embedded in the compiled component as a target ABI |
| 6 | revision, which indicates the semantics the component expects from the |
| 7 | platform. |
| 8 | |
| 9 | Updates to the `fuchsia_target_api_level` are currently done manually. As a |
| 10 | general rule, we want to be using the latest API level supported by the Fuchsia |
| 11 | SDK checked out. An older API level might be needed if one of the following are |
| 12 | true: |
| 13 | |
| 14 | 1. There are unresolved compatibility issues. |
| 15 | 2. The binaries are intended to ship on an older release of Fuchsia. |
| 16 | |
| 17 | For instance, if M97 is shipped on a Fuchsia release that only supports API |
| 18 | level up to 5, the target API level cannot be updated in Chromium until M97 |
| 19 | branch is cut. |
