summaryrefslogtreecommitdiff
path: root/docs/meson.build
Commit message (Collapse)AuthorAgeFilesLines
* docs: Don't install in doc/pango/reference folderVanadiae2022-02-241-1/+1
| | | | | | | | | | | | | | | | Currently Devhelp (and hence Builder) cannot find the pango documentation, which means that all pango classes/enums links from GTK open the online version of the pango docs instead of using the local one. This is because pango installs its documentation in a subfolder under $datadir/doc/pango/reference instead of $datadir/doc/pango*/ where devhelp would be able to detect the pango*.devhelp2 file and hence show the pango docs. I assume the reason to put those docs in a subfolder is to keep the pango docs "tidy" since there can be 6 of them. But not having them available in devhelp makes the whole point of having docs installed moot, and as such I believe the inconvenient of having 6 different Pango* documentation in the devhelp list are less important than being able to actually use the offline installed documentation. Hence this commit changes the docs install directory to $datadir/doc.
* docs: Don't build pangoot bits if not enableddoc-no-pangootChun-wei Fan2021-12-171-23/+23
| | | | | PangoOT is actually a part of PangoFT2, so don't attempt to build its docs if FontConfig is not found.
* Add docs for new attributesMatthias Clasen2021-09-011-0/+2
|
* doc: Update pango_glyph_string_index_to_xMatthias Clasen2021-08-261-0/+2
| | | | | | What the docs were saying is no longer strictly true, now that we are using font metrics. Update them, and add an illustration.
* docs: Add another illustrationMatthias Clasen2021-08-261-0/+2
| | | | Show cursor positions.
* Add an illustration for caret metricscaret-slopeMatthias Clasen2021-08-241-0/+2
|
* docs: Add another illustrationdoc-font-metricsMatthias Clasen2021-08-221-1/+3
| | | | Show font metrics.
* docs: Add an example for split cursorsMatthias Clasen2021-08-091-0/+3
| | | | | | | Show how weak and strong cursors look in practice. Fixes: #77
* docs: Add one more dark mode imageMatthias Clasen2021-08-081-1/+2
|
* docs: Add some more imagesMatthias Clasen2021-08-081-0/+4
| | | | Add a visual example of bidi reordering.
* docs: Add a dark mode variant of some imagesMatthias Clasen2021-08-081-2/+4
|
* docs: Fix up deps for imagesMatthias Clasen2021-08-081-0/+13
| | | | We have two lists to keep in sync :(
* build: Install documentationinstall-docsEmmanuele Bassi2021-03-121-0/+14
| | | | We are building it, but never installing it on the system.
* docs: Convert the pangocairo section to pango_cairo.mdMatthias Clasen2021-03-111-0/+1
|
* docs: Convert bidi and vertical sections to pango_bidi.mdMatthias Clasen2021-03-111-0/+1
|
* docs: Convert fonts section to pango_fonts.mdMatthias Clasen2021-03-111-0/+1
|
* docs: Convert markup and attributes docs to pango_markup.mdMatthias Clasen2021-03-111-0/+1
|
* docs: Convert rendering section to pango_rendering.mdMatthias Clasen2021-03-111-0/+1
|
* Generate Pango API docs with gi-docgenMatthias Clasen2021-03-111-79/+140
| | | | | | | | | | | | | | | | | | | Stop using gtk-doc, and switch to gi-docgen. The gi-docgen tool generates API references through the introspection data, which has various benefits: - it does not parse C code - it does not generate and run C code to introspect types at build time - it does not present a different API from the one we're exporting Additionally, gi-docgen: - does not generate DocBook XML in order to generate HTML - does not go through xsltproc - parses proper Markdown Which makes it markedly faster than gtk-doc has ever been.
* build: Use correct check for pango-xft API referenceEmmanuele Bassi2020-04-141-1/+1
| | | | PangoXft depends on both Xft and fontconfig.
* build: Do not use source/build_root functionsEmmanuele Bassi2020-04-141-2/+1
| | | | | Meson has the include_directories() object to specify inclusion paths that refer to both the source and build directories.
* Improve docs buildMatthias Clasen2019-08-131-22/+3
| | | | | | | We want to include api docs for platform-specific apis. Avoid getting build failures for introspection by explictly generating a types file with only the linux types.
* docs: Add extent imagesMatthias Clasen2019-08-041-0/+2
| | | | Add an illustration of logical and ink rects.
* Remove unused remnants of shape engineKhaled Hosny2019-07-191-1/+0
|
* Add some more docsMatthias Clasen2019-07-131-0/+1
|
* docs: Update private header listMatthias Clasen2019-07-121-3/+8
|
* Update docsMatthias Clasen2019-07-051-1/+1
| | | | Make a new image for layout parameters.
* meson: skip pangoxft headers for the Windows gtk-doc buildChristoph Reiter2018-04-091-0/+5
| | | | | | | The API isn't available on Windows and gtk-doc fails with a linker error otherwise. https://bugzilla.gnome.org/show_bug.cgi?id=795045
* meson: Check for HarfBuzz and FontConfig for PangoFT2Chun-wei Fan2018-03-301-1/+1
| | | | | | | | | | | | | | | | | | | | | It is possible that we can have the following situations, at least on Windows: -FreeType present, FontConfig missing -Cairo-FT present, with no FontConfig support. As gen-script-for-lang requires FontConfig, and PangoFT2 depends on HarfBuzz, FontConfig and Freetype, we need to check for them before we build PangoFT2, and so that we could include PangoFT2 support in PangoCairo. The tests and pango-view have an optional dependency on PangoFT2, so we need to also check whether we built PangoFT2 before we try to build things related to PangoFT2. For the tools, since gen-script-for-lang.c depends on FontConfig, check for it as well before we build it. https://bugzilla.gnome.org/show_bug.cgi?id=783274
* Drop mention of long gone filesKhaled Hosny2018-03-141-1/+0
|
* Modules are long goneKhaled Hosny2018-03-141-1/+0
|
* Drop now unused mini-fribidiKhaled Hosny2018-02-041-1/+0
|
* meson: Add a few missing things, minor fixes, TODONirbheek Chauhan2017-05-191-2/+2
|
* build: Add Meson build systemEmmanuele Bassi2017-05-191-0/+108
Meson is a meta build system that is: - fast - simpler to understand and use - portable to multiple platforms through different backends - well integrated with the GNOME platform - well maintained Using Meson allows us to build Pango much more quickly, and on all the platforms we currently target, without any loss of functionality, compared to Autotools. Some timing comparisons with hot ccache for both build systems: * autogen.sh: * meson real 0m11.149s real 0m2.525s user 0m8.153s user 0m1.609s sys 0m2.363s sys 0m1.206s * make -j$(($(nproc) + 2)) * ninja real 0m9.186s real 0m3.387s user 0m16.295s user 0m6.887s sys 0m5.337s sys 0m1.318s -------------------------------------------------------------- * autotools * meson + ninja real 0m27.669s real 0m5.772s user 0m45.622s user 0m8.465s sys 0m10.698s sys 0m2.357s System: Intel Core i7-7500U, SSD, 16GB of RAM