| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
| |
It was added my mistake. This is not new
harfbuzz api.
|
|
|
|
|
| |
Most fonts are not color, no need to
check that for every glyph.
|
|
|
|
|
|
|
|
|
|
| |
Subprojects that use meson.override_dependency() do not require the
caller to provide the subproject name and dependency variable name
inside the subproject.
All the dependencies we use can be switched in this way; including
gi-docgen which is now automatically executed by the find_program()
invocation thanks to `program_names` in the wrap file.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The is_msvc_like change is wrong; it used a false correlation between
"compiler being used" and "dependency method" by saying that on
Windows, when building with MSVC, you will only use CMake to find
freetype.
You can use pkgconfig to find freetype on Windows with MSVC -- when
it has been built with meson (msvc). You can also find freetype
using CMake on other platforms like macOS or Linux.
The solution is simple: just search for both names on all platforms,
and just search for the pkgconfig name first.
This requires Meson 0.60
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the same change that was made for pangocairo earlier.
Without this, the pc file contains the following requires line:
```
Requires: pango,
```
Which is incorrect, and also invalid.
|
| |
|
|
|
|
|
|
|
| |
This caused issues when buliding HarfBuzz as a fallback subproject, as
mentioned in issue #707, so don't use platform APIs in HarfBuzz on
Windows as a result.
This reverts commit 3ab3e076665d0722d6f12938f3bddf263322539b.
|
|
|
|
|
| |
We are not using these HAVE_FOO defines anymore.
So no need to produce them.
|
|\
| |
| |
| |
| | |
Pango-1.x: Add some DirectWrite support as a supplement
See merge request GNOME/pango!635
|
| |
| |
| |
| |
| |
| |
| |
| | |
These support are not enabled by default when building HarfBuzz, but if one or
both are enabled, we can simplify the codepath to create the needed hb_face_t.
This was not added previously as the needed HarfBuzz GDI API was not available
at the time the code was written and we are only integrating DirectWrite now.
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
...in Cairo, as well as their presence in the Windows SDKs (which should
always be there in the Windows SDKs). We want to use items in DirectWrite
to help us improve support on Windows regarding looking up for features
(description) of a font.
Since upstream Cairo gained DirectWrite support very recently, check for
it only via pkg-config, since Cairo had Meson build support quite a bit before
that happened.
|
| |
| |
| |
| |
| | |
Trying to get back into the habit of bumping
the version in git right after a release.
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
This reverts commit e5b62c8c27599699fa583a18e5346138799d9f50.
No longer needed. We've renamed everything to avoid
conflicts, instead.
|
|
|
|
|
|
|
|
| |
Having both pango 1.x and pango 2 linked into
the same process will cause trouble, because the
type and function names conflict.
Error out if we detect this situation.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Use CMake's built-in support to look for FreeType2 on Visual Studio-like
builds, by using the 'freetype' package name, since it is what CMake expects.
This cleans the Meson build files a bit and CMake would do more comprehensive
work to help us find FreeType.
|
|
|
|
| |
Drop items that are actually not used.
|
|
|
|
|
|
|
|
|
|
|
| |
Pango 1.50.x and later require a HarfBuzz version that is buildable via
Meson, so we can just use the standard dependency() call for HarfBuzz
for all builds.
This means that we can drop all the items where we search for HarfBuzz
manually.
Also remove the stray HarfBuzz items that are no longer used.
|
|
|
| |
Cairo is a proper meson project now, and force-enabling fontconfig and freetype broke the CI build on MacOS.
|
|
|
|
| |
No need to check harfbuzz_dep. We require it.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Replace json-glib by a homegrown json parser/printer.
|
| |
|
|
|
|
| |
That is what we have in ci.
|
|
|
|
|
| |
I hope this will give some insight into what is
happening in ci builds.
|
|
|
|
| |
This is necessary for ci on MacOs to build.
|
|
|
|
|
|
|
|
| |
Add api to serialize PangoLayout, for the benefit
of testing and debugging. Currently, this uses
json, but that is an implementation detail.
Some tests included.
|
|
|
|
|
|
|
| |
We are using the hb metrics api in more places
now, so just require 2.6.0 where it was introduced.
That version is almost 2 years old now, so that
is hopefully not too much of a burden.
|
|
|
|
|
| |
This version of fontconfig has all the API
we are using, and was released in 2018.
|
| |
|
| |
|
|
|
|
|
| |
Also fix CoreText detection by including its header. (Older systems have
CoreText as a private framework.)
|
| |
|
|
|
|
|
|
| |
Now that the code has been fixed, we can enable
these warnings. The flags here match what is used
in GTK.
|
|
|
|
|
|
| |
Pango uses the FRIBIDI_TYPE_RLI macro. It was not usable until fribidi
commit 46f52d588ab5 ("Fixed bug PFRIBIDI_TYPE_PDF_LRI is undefined.
Issue #69") which was first included in v1.0.6.
|
|
|
|
| |
We're going to add api.
|
|
|
|
|
|
|
| |
We are using hb_ot_var apis in various places.
These have been introduced in harfbuzz 2.2.0.
2.2.0 is from 2018, so this should be safe.
|
| |
|
| |
|