summaryrefslogtreecommitdiff
path: root/pango/meson.build
Commit message (Collapse)AuthorAgeFilesLines
* pangowin32: Initialize DirectWriteChun-wei Fan2022-09-261-0/+1
| | | | | We set up the boilerplate that is necessary for using DirectWrite in our code. Also add code to tear it down after we are done with it.
* build: Check for DirectWrite supportChun-wei Fan2022-09-261-0/+1
| | | | | | | | | | | ...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.
* Update gir dependenciesMatthias Clasen2022-06-271-1/+1
| | | | | This is necessary to make GListModel show up as implemented interface in the docs.
* Meson: Clean up HarfBuzz searchChun-wei Fan2022-02-211-12/+4
| | | | | | | | | | | 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.
* Install pango-fontset-simple.hMatthias Clasen2021-12-251-0/+1
|
* Split off PangoFontsetSimpleMatthias Clasen2021-12-231-0/+1
| | | | Put PangoFontsetSimple into its own files.
* serializer: Replace json-glibMatthias Clasen2021-12-021-0/+2
| | | | Replace json-glib by a homegrown json parser/printer.
* Add layout serialization apiMatthias Clasen2021-11-181-0/+1
| | | | | | | | 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.
* Some more code reorgMatthias Clasen2021-08-201-1/+0
| | | | | We use harfbuzz shaping on all platforms now, so just merge the code into shape.c
* Some code reorgMatthias Clasen2021-08-201-0/+1
| | | | | Split the itemization code into its own file, and move things around a bit.
* Cosmetics: Split off pango-color.hMatthias Clasen2021-08-201-0/+1
|
* Cosmetics: Split off pango-markup.hMatthias Clasen2021-08-201-0/+1
|
* build: Don't build HarfBuzz prematurelyhb-dont-fallback-too-earlyChun-wei Fan2021-02-251-2/+13
| | | | | | | | | | | | | | | | For Visual Studio builds, since HarfBuzz is built with CMake until HarfBuzz 2.6.x yet we only require HarfBuzz 2.0.0 or later, we aren't able to find pre-2.6.x HarfBuzz using Meson's dependency() method as the support for CMake config files is not done in Meson. As a result, we need to make sure that we first manually look for the HarfBuzz/HarfBuzz-GObject libraries before we attempt to use the fallback mechanism in Meson, so that we won't rebuild HarfBuzz unneccesarily. This rebuild will also cause issues for older compilers that don't have enough support for C++11 as building Harfbuzz with Meson support requires a C++11 compiler, which was mandated in HarfBuzz 2.5.0.
* Leave pango-version-macros.h out of the girgir-fixesMatthias Clasen2021-02-151-2/+3
| | | | | PANGO_VERSION_MIN_REQUIRED is a build utility, and is not useful as a constant in the gir. Leave it out.
* Include version macros in the girMatthias Clasen2021-02-151-2/+2
| | | | | PANGO_MAJOR/MINOR/MICRO_VERSION are useful to have in the gir.
* meson: add harfbuzz gobject dependencyStéphane Cerveau2021-01-131-1/+6
| | | | | | | | When harfbuzz is built as a subproject, the gobject dep should be used to generate the gir. The build was failing when the harfbuzz gir was not available system wide.
* Merge branch 'override-dependency' into 'master'Matthias Clasen2020-10-141-0/+5
|\ | | | | | | | | meson: Use meson.override_dependency() See merge request GNOME/pango!250
| * meson: Use meson.override_dependency()Xavier Claessens2020-09-301-0/+5
| | | | | | | | | | This allows projects that use pango as a subproject to not hardcode dependency variable names such as 'libpangocairo_dep'.
* | meson: Change introspection option to yielding featureXavier Claessens2020-09-301-1/+2
|/ | | | | | | Yielding option means that if pango is built as a subproject, it will take the value of that option from the parent project (e.g. gst-build). For that to work it must be of the same type, which is "feature" instead of "boolean" in all GStreamer modules.
* Revert "meson: Change introspection option to yielding feature"Matthias Clasen2020-09-301-2/+1
| | | | | | | This reverts commit 82cfabbabaade239beb26136cb28c98156552ea5. This change broke GTK ci, and it takes more work to fix it than I can invest atm. We can try again when GTK is ready for it.
* meson: Change introspection option to yielding featureXavier Claessens2020-09-291-1/+2
| | | | | | | Yielding option means that if pango is built as a subproject, it will take the value of that option from the parent project (e.g. gst-build). For that to work it must be of the same type, which is "feature" instead of "boolean" in all GStreamer modules.
* Add sysprof tracing supportMatthias Clasen2020-08-191-0/+1
| | | | | Add support for adding sysprof marks. Strongly inspired by equivalent GLib support.
* Include HarfBuzz when generating introspection dataEmmanuele Bassi2020-06-111-1/+1
| | | | | | | | | | The Pango API exposes harfbuzz types, and so we need to depend on HarfBuzz-0.0 when generating our introspection data. The introspection data on HarfBuzz was fixed upstream, even though the current introspected API is not stellar. Fixes: #458
* Use the appropriate namespace for Pango sub-librariesEmmanuele Bassi2020-06-101-5/+5
| | | | | | | | | | | | | | | | | | | | The Pango sub-libraries have symbols in the pango_<something> namespace, but the identifiers are in the Pango one, which makes consumers of the introspection data either get something like: PangoCairo.show_layout() with a bunch of warnings caused by the type macros not following the appropriate pattern, or: PangoCairo.cairo_show_layout() which breaks introspection ABI. We can use the __GI_SCANNER__ pre-processor symbol to trick the scanner into generating the appropriate representation of the API, while keeping the C consumers happy with the existing—albeit wildly inconsistent with best practices for GObject-based libraries—symbols.
* Use the correct identifier for Pango sub-librariesEmmanuele Bassi2020-06-101-5/+5
| | | | | | | | The Pango sub-libraries sadly hijack the Pango namespace for their symbols, but use a different namespace for the identifiers. This fixes an introspection ABI incompatible change that made its way in Pango 1.45.
* build: Generate pkg-config files for PangoOT and PangoFcEmmanuele Bassi2020-06-081-4/+20
| | | | | Since we have them as separate namespaces, we need separate pkg-config file in order to let Vala consume them.
* build: Remove unnecessary argumentsEmmanuele Bassi2020-06-081-8/+0
| | | | | The pkgconfig.generate() function has default values for the version and installation path argument, and we're already using them.
* build: Generate the correct introspection symbolsEmmanuele Bassi2020-06-081-12/+12
| | | | | | | | The prefix for the Pango sub-libraries is still Pango, so we need to ensure that the symbols and identifiers are correctly matched. This partially reverts !175, as Pango does not have separate pkg-config files for pango-ot and pango-fc.
* meson: Fix pkg-config file generation for HarfBuzzChun-wei Fan2020-06-051-1/+6
| | | | | HarfBuzz may be found manually instead of via pkg-config, so only add it to Pango's pkg-config file if it is really found via pkg-config.
* Use correct c:include and distinct package in PangoFc-1.0 and PangoOT-1.0Rico Tzschichholz2020-02-251-4/+4
| | | | Fixes: #456
* Revert "Include HarfBuzz when generating introspection data"Michael Catanzaro2020-02-111-1/+1
| | | This reverts commit 7cfef2b4604ceb64d9022e02a11e6963c7f1289d
* Include HarfBuzz when generating introspection dataEmmanuele Bassi2020-02-071-1/+1
| | | | | | | The Pango API exposes harfbuzz types, and so we need to depend on HarfBuzz-0.0 when generating our introspection data. Fixes: #458
* Install PangoFc and PangoOT GObject-IntrospectionSimon McVittie2019-08-101-0/+2
| | | | | | | | | | | | | If we don't install these, we can't load PangoXft and PangoFT2, which depend on them: $ GI_TYPELIB_PATH=${DESTDIR}/usr/lib/x86_64-linux-gnu/girepository-1.0 python3 ... >>> from gi.repository import PangoXft ... gi.RepositoryError: Typelib file for namespace 'PangoOT', version '1.0' not found Signed-off-by: Simon McVittie <smcv@debian.org>
* build: Install pango-ot headersEmmanuele Bassi2019-08-031-1/+1
| | | | | The refactoring of commit 1bdadfe1aae158fb406e10f81f3ae0533dea1602 missed out an installed header.
* Parse all pangoft sourcesEmmanuele Bassi2019-08-021-4/+3
| | | | | | The PangoFT2 sources have gtk-doc stanzas, so we need to parse them all to avoid warnings from the introspection scanner only having the headers to go by.
* Decouple PangoOT and PangoFc from PangoFT2Emmanuele Bassi2019-08-021-13/+58
| | | | | | | | | | | | | | | | | The PangoFT2 introspection namespace contains symbols from two other namespaces on top of its own PangoFT2 symbols: - PangoOT, the deprecated wrapper for FreeType's OpenType API - PangoFc, the wrapper for FontConfig's API We can only have one namespace per GIR/typelib, so we need to decouple the GIR and typelib introspection data from PangoFT2 into three separate namespaces. These are just new introspection namespaces mapping to their corresponding C symbols; there are no new shared libraries: if you're using PangoFc and PangOT API then you must be linking against libpangoft2 anyway.
* pkgconfig: Make harfbuzz a RequiresMatthias Clasen2019-07-281-1/+1
| | | | | It used to be Requires.private, but we expose harfbuzz types in public headers now.
* Merge branch 'cairo-detection-improvements' into 'master'Matthias Clasen2019-07-211-1/+9
|\ | | | | | | | | Improve build experience in regards to Cairo/PangoCairo See merge request GNOME/pango!93
| * pango/meson.build: Fix pangocairo.pc on MSVC buildsChun-wei Fan2019-07-191-1/+9
| | | | | | | | | | | | | | On MSVC builds, Cairo may be found either via pkg-config files or manually through finding headers and libs, so we need to ensure that we create pangocairo.pc correctly, otherwise items that depend on PangoCairo may not link correctly.
* | Remove now unused platform shaping codeKhaled Hosny2019-07-191-5/+0
|/
* Move _pango_fc_shape to libpangoMatthias Clasen2019-07-181-1/+1
| | | | | | | We temporarily export it since it is still used for the shape engine in libpangoft2. This will be undone when we drop the shape engine.
* Revert "Reduce overlinking"Matthias Clasen2019-07-121-3/+5
| | | | This reverts commit f972ba0562823a8d55ad02ff9609481a884c79f8.
* Revert "Move pangofc to libpango"Matthias Clasen2019-07-121-22/+8
| | | | This reverts commit 8b85815f1b122842d915e7fc29cc68d228a64dbb.
* Move pangofc to libpangoMatthias Clasen2019-07-091-8/+22
| | | | | Move the fontconfig+harfbuzz using parts to libpango, since we want to start using harfbuzz on all platforms.
* Reduce overlinkingMatthias Clasen2019-07-091-5/+3
| | | | | Only link libpangoxft and libpangocairo against xft and cairo.
* Header cleanupMatthias Clasen2019-07-041-4/+0
| | | | | | | Abolish the PANGO_ENABLE_BACKEND and PANGO_ENABLE_ENGINE defines. All backend-only apis are moved into private headers, all apis that were engine-only are marked as deprecated, since engines are.
* meson: Use 'standard' option namesMatthias Clasen2019-07-011-1/+1
| | | | | | | | Use 'gtk_doc' for documentation and 'introspection' for, well, introspection. This matches what the rest of the stack does. Fixes https://gitlab.gnome.org/GNOME/pango/issues/364
* pango.pc: Make gobject-2.0 a non-private requirementTom Schoonjans2018-12-191-0/+1
|
* Fix fallout from bidi deprecationMatthias Clasen2018-12-111-0/+1
| | | | | | | PangoDirection is still used in some public apis, so just keep it around. Closes: #339
* meson: Set the compatibility version correctly on macOSNirbheek Chauhan2018-10-121-0/+4
| | | | | | Requires the latest Meson. Closes https://gitlab.gnome.org/GNOME/pango/issues/320
View Lorry Controller Status