| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
| |
We use hb_variation_t that was added in harfbuzz 1.4.2.
|
|
|
|
| |
I’m assuming the new API is thread-safe as claimed.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Many of Pango's dependencies do not support a build system for Visual
Studio that would generate the pkg-config files for them, so we need to
try to look for them using cc.has_header() and cc.find_library() for
them, namely for Cairo, FreeType, FontConfig and HarfBuzz as fallbacks.
For Cairo, things are more complicated as there are multiple build
options and configurations for it, so we need to check for those that we
need after we find the Cairo headers and libraries by:
-Including the respective headers (for cairo-win32.h, cairo-ps.h,
cairo-pdf.h, cairo-quartz.h and cairo-xlib.h, since these features
must have been enabled when Cairo is built and installed in order for
those headers to be succesfully included)
-For pangocairo with FreeType support, we need to check whether the
FontConfig support is built into Cairo as well, as FontConfig support
is actually required in Cairo for this.
-For Cairo/PNG output surface support, check whether Cairo is built with
PNG output surface support.
We also need to update how pangocairo.pc and pangoft2 are generated:
-On builds where pkg-config files can be found for cairo, freetype,
fontconfig and/or harfbuzz:
Generate it with "Requires: pango <depedencies>" as before, otherwise
for MSVC builds where we find these libraries manually, we don't put
these packages under "Requires:..." or "Requires.private:...", but
instead put them under "Libs:", linking to each dep as -l<.lib file
name>
This is so that pangocairo.pc and pangooft2.pc can be correctly used by
items that need to make use of it, such as g-ir-scanner.
https://bugzilla.gnome.org/show_bug.cgi?id=783274
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
We've added new API for font variations.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
| |
Changes from 1.40.8:
- Build and dist fixes
- Fix build on Windows with MSVC (#783274)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
No other library in the stack ships them any more, and they are of
dubious use.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This updates the autotools scripts to support Visual Studio 2017 builds, by copying
the Visual Studio 2010 projects and updating items in there as necessary.
Note the format of the toolset version changed, so we allow one to specify a
custom toolset version string and hence use it if it is specified, otherwise
the toolset version string is generated as it was before.
Since Visual Studio 2017 aims to be compatible on the CRT level as Visual Studio
2015, the 2017-compiled binaries should be usable without problems with 2015-compiled
binaries.
|
|
|
|
|
|
|
| |
This allows one to go down one less level in the directory tree to get to the
Visual Studio project files, and so make things more in line with the rest of
the GTK+ stack. This also cleans up the Visual Studio 201x projects as there
are some items that can be actually combined.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Add a configure check to see whether compiler directives are available
for exporting symbols, and use them if so. Likewise, update
the Visual Studio projects and config.h.win32.in to do likewise for
Windows builds.
We can then drop the .def files that were used to export symbols on
Windows builds, which should clean up things a bit.
|
|
|
|
|
| |
This is used to generate the .pc files to make generating introspection
files easier for packages that depend on Pango.
|
| |
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=764191
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Pango uses the HB_VERSION_ATLEAST macro, but it was only
defined in HarfBuzz 0.9.30. Thus, compiling with an older
version fails.
Signed-off-by: Manuel Bachmann <manuel.bachmann@iot.bzh>
https://bugzilla.gnome.org/show_bug.cgi?id=756015
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
This "adds" Visual Studio 2015 projects in the way that we did before:
copy the Visual Studio 2010 projects and replacing the items in there
as necessary.
Oh, this does pass 'make -jN distcheck' :)
|
| |
|
| |
|
| |
|
|
|
|
|
| |
This is so I can require a bleeding-edge pango in GTK+ for
a font feature demo.
|
| |
|
|
|
|
| |
Fixes https://bugzilla.gnome.org/show_bug.cgi?id=694697
|
| |
|
| |
|
|
|
|
|
|
|
| |
This should complete the kill-modules effort. What is left is leftover
removal and unbreaking stuff.
Bug 733882 - Kill Pango modules, engines, and config files
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Now shaper is discovered via (previously unused!) font->find_shaper().
I'm keeping that just to allow clients override shaping. Though,
even that I'm not sure we want to keep.
Wraps shaper in PangoEngineShape structs to keep PangoAnalysis API
intact.
Deprecated pango-modules.h and some pango-engine.h. Language modules
are not moved yet.
Wired up PangoFc, PangoWin32, and PangoCoretext shapers.
|
|
|
|
| |
Note wired up yet. Doesn't build.
|