JDK-8193017 : Import freetype sources into OpenJDK source tree
- Type: Bug
- Component: client-libs
- Sub-Component: 2d
- Affected Version: 11
- Priority: P3
- Status: Resolved
- Resolution: Fixed
- Submitted: 2017-12-04
- Updated: 2024-07-12
- Resolved: 2018-03-12
The Version table provides details related to the release that this issue/RFE will be addressed.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
Unresolved : Release in which this issue/RFE will be addressed.
Resolved: Release in which this issue/RFE has been resolved.
Fixed : Release in which this issue/RFE has been fixed. The release containing this fix may be available for download as an Early Access Release or a General Availability Release.
To download the current JDK release, click here.
| JDK 11 |
|---|
11 b05Fixed  |
Related Reports
|
Relates :
|
Description
OpenJDK builds have always required freetype which is only available as a system library on Linux. On Windows and Mac developers need to build freetype separately and then point to that pre-built freetype as part of the configure process. This then gets bundled into the JDK so that it is available at run time. The way linking works on Mac the libfontmanager.dylib this requires an extra step (only very recently fixed, see https://bugs.openjdk.java.net/browse/JDK-8139653) And once you are shipping a library like freetype, you want to keep it up to date. Once build infrastructure needs to be updated to get this updated version it is getting harder to do that, without much advantage .. the size of the freetype sources and the time to build it are both insignificant. So updating the version in the source is much easier and transparent. None of this need require that a Linux (or Solaris) build should use the JDK version. Those can continue to use the system version if so preferred. And it will make life a lot easier for people building OpenJDK on Windows and Mac .. it has been a pain point for a long time.
Comments
|