summaryrefslogtreecommitdiff
path: root/meson_options.txt
Commit message (Collapse)AuthorAgeFilesLines
* build: Only use fallback dep for FontConfig when needed/requestedChun-wei Fan2019-07-191-0/+4
| | | | | | | | | | | | | Windows and macOS only optionally requires FontConfig, so: -Add an option, for Windows and macOS, whether we want to use FontConfig on these platforms. This is ignored on *NIX, where FontConfig will always be used. -We still look for FontConfig first via pkg-config files, and on MSVC builds, via looking for its headers and .lib files. If FontConfig is required (or requested) but is not found, we then use the fallback dependency for it.
* Make installed tests optionalMatthias Clasen2019-07-061-0/+4
| | | | Closes: https://gitlab.gnome.org/GNOME/pango/issues/354
* meson: Use 'standard' option namesMatthias Clasen2019-07-011-2/+2
| | | | | | | | 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
* meson: Update rules for introspectionEmmanuele Bassi2018-02-121-0/+4
| | | | | | | | | | | | | | | Building introspection should not be gated on cross-compilation: it's perfectly acceptable to use an helper binary to run the introspection scanner when cross-compiling — in fact, it's what projects like Yocto do. Instead, we should have an option to disable the introspection generation explicitly. Additionally, when building introspection data for ancillary Pango libraries, like PangoCairo or PangoXft, we should depend on the GIR target, instead of adding an `--include-uninstalled` extra argument for the introspection scanner; this allows building Pango as a sub-project of another project, and lets Meson deal with the appropriate paths and arguments when invoking the scanner.
* meson: Add a few missing things, minor fixes, TODONirbheek Chauhan2017-05-191-2/+2
|
* build: Add Meson build systemEmmanuele Bassi2017-05-191-0/+4
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