You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Mar 7, 2025. It is now read-only.
Most libgdiplus packages are built without --with-pango and .NET users are forced to build the library from source to get the advanced typography features working. This need for building from source is not obvious to the end users (there are multiple issues in dotnet/runtime repo attesting to that) or the package maintainers.
Back in 2018, some package management systems were having pango < v1.38 and therefore marking the pango dependency mandatory for libgdiplus (which at the time worked with pango >= v1.38) was not feasible: #269 (comment).
However, now the situation (based on my research) is so; all relevant packaging systems with libgdiplus v6x also have pango > 1.40. Distros, such as Ubuntu 18.04, which have older pango are also not upgrading libgdiplus for some time (bionic is still having libgdiplus v4x). Later versions of Ubuntu have both pango 1.4x and libgdiplus v6x. Therefore marking pango as required dependency is safe.
Suggestion for next libgdiplus version:
remove --with-pango argument.
error when --with-pango argument is provided during configure: Remove `--with-pango` as pango is now a required dependency.
add --without-pango argument with a *WARNING* - some typrography / text rendering features will not work without pango. Consider removing `--without-pango` and adding the dependency.