| 3 | | We are aware that Linux distributions and embedded systems vendors like to be able to compile everything with the same system build toolchain, which may be very old, so we have compromised with Apple to develop a [[DependenciesPolicy]] that attempts to balance the interests of both WebKit distributors and developers. We intend to support some system compiler in the latest Ubuntu LTS and Debian stable releases until one year after the subsequent release, but, depending on the age of the release, this might be some version of Clang rather than GCC. We no longer provide any timeline as to how long a particular version of GCC may be supported, as this decision will be made by WebKit developers on a case-by-case basis. However, we will always support the version of libstdc++ available in these releases until one year after the subsequent release. Preserving compatibility with older standard library versions is necessary to allow updates on older systems, even if a newer compiler is used to build those updates. In general, you can expect a new standard library version to be supported by WebKit for approximately three to four years, in accordance with the dependencies policy. |
| | 3 | We are aware that Linux distributions and embedded systems vendors like to be able to compile everything with the same system build toolchain, which may be very old, so we have compromised with Apple to develop a [[DependenciesPolicy]] that attempts to balance the interests of both WebKit distributors and developers. We intend to support some system compilers in the latest Ubuntu LTS and Debian stable releases until one year after the subsequent release, but, depending on the age of the release, this might be some version of Clang rather than GCC. We no longer provide any timeline as to how long a particular version of GCC may be supported, as this decision will be made by WebKit developers on a case-by-case basis. However, we will always support the version of libstdc++ available in these releases until one year after the subsequent release. Preserving compatibility with older standard library versions is necessary to allow updates on older systems, even if a newer compiler is used to build those updates. In general, you can expect a new standard library version to be supported by WebKit for approximately three to four years, in accordance with the dependencies policy. |
| 16 | | * WebKitGTK or WPE WebKit 2.24 (released March 2019) both support GCC 6 |
| 17 | | * WebKitGTK or WPE WebKit 2.26 (scheduled for September 2019) will be the first release to require GCC 7 (due to a one-time compromise with Apple to end support for Debian Stretch early) |
| 18 | | * WebKitGTK or WPE WebKit 2.34 (scheduled for September 2021) is expected to be the first release to require libstdc++ 8 |
| 19 | | * WebKitGTK or WPE WebKit 2.38 (scheduled for September 2022) or 2.40 (scheduled for March 2023) is expected to be the first release to require libstdc++ 9 |
| | 16 | |
| | 17 | This policy affects the trunk. For the already released versions, these are the minimum supported GCC versions: |
| | 18 | |
| | 19 | ||= Release =||= Date =||= Required GCC version =|| |
| | 20 | || 2.36 (trunk) || Unreleased || 8.3 || |
| | 21 | || 2.34 || September 2021 || 7.3 || |
| | 22 | || 2.32 || March 2021 || 7.3 || |
| | 23 | || 2.30 || September 2020 || 7.3 || |
| | 24 | || 2.28 || March 2020 || 7.3 || |
| | 25 | || 2.26 || September 2019 || 7.3 || |
| | 26 | || 2.24 || March 2019 || 6.0 || |
| | 27 | |
| | 28 | More info about WebKitGTK stable release in the [[WebKitGTK/StableRelease]] page. |