• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

src/H30-Mar-2022-120,39184,052

AUTHORSH A D30-Mar-2022201 1514

COPYINGH A D30-Mar-20221.8 KiB3932

Makefile.amH A D30-Mar-20222.3 KiB9774

NEWSH A D30-Mar-202273.4 KiB2,4671,872

README-mozillaH A D03-May-20221.2 KiB2921

README.mdH A D30-Mar-20221.8 KiB3421

THANKSH A D30-Mar-2022129 87

TODOH A D30-Mar-2022436 2915

autogen.shH A D30-Mar-20221.1 KiB4933

configure.acH A D30-Mar-202214.3 KiB485422

git.mkH A D30-Mar-202212.3 KiB401293

harfbuzz.doapH A D30-Mar-2022775 2521

update.shH A D30-Mar-2022949 3320

README-mozilla

1This directory contains the HarfBuzz source from the upstream repo:
2https://github.com/harfbuzz/harfbuzz
3
4Current version: 2.8.1 [commit b37f03f16b39d397a626f097858e9ae550234ca0]
5
6!!!Please Note!!!
7Because LLVM added in D100581 support for -Wunused-but-set-parameter and -Wunused-but-set-variable
8and clang doesn't cope well with `#pragma GCC diagnostic warning` vs gcc we had to patch this version up.
9The same patch was upstream in #2995 so, starting with the next version, the current patch will no longer
10be needed.
11
12UPDATING:
13
14Our in-tree copy of HarfBuzz does not depend on any generated files from the
15upstream build system. Therefore, it should be sufficient to simply overwrite
16the in-tree files one the updated ones from upstream to perform updates.
17
18To simplify this, the in-tree copy can be updated by running
19  sh update.sh
20from within the gfx/harfbuzz directory.
21
22If the collection of source files changes, manual updates to moz.build may be
23needed as we don't use the upstream makefiles.
24
25The in-tree copy may be omitted during build by --with-system-harfbuzz.
26Make sure to keep pkg-config version check within toolkit/moz.configure in sync
27with checkout version or increment latest tag by one if it's not based
28on upstream release.
29

README.md

1[![Linux CI Status](https://github.com/harfbuzz/harfbuzz/workflows/linux-ci/badge.svg)](https://github.com/harfbuzz/harfbuzz/workflows/linux-ci/badge.svg)
2[![CircleCI Build Status](https://circleci.com/gh/harfbuzz/harfbuzz/tree/master.svg?style=svg)](https://circleci.com/gh/harfbuzz/harfbuzz/tree/master)
3[![OSS-Fuzz Status](https://oss-fuzz-build-logs.storage.googleapis.com/badges/harfbuzz.svg)](https://oss-fuzz-build-logs.storage.googleapis.com/index.html)
4[![Coverity Code Health](https://img.shields.io/coverity/scan/5450.svg)](https://scan.coverity.com/projects/behdad-harfbuzz)
5[![Codacy Code Health](https://api.codacy.com/project/badge/Grade/f17f1708783c447488bc8dd317150eaa)](https://app.codacy.com/app/behdad/harfbuzz)
6[![Codecov Code Coverage](https://codecov.io/gh/harfbuzz/harfbuzz/branch/master/graph/badge.svg)](https://codecov.io/gh/harfbuzz/harfbuzz)
7[![Coverals Code Coverage](https://img.shields.io/coveralls/harfbuzz/harfbuzz.svg)](https://coveralls.io/r/harfbuzz/harfbuzz)
8[![Packaging status](https://repology.org/badge/tiny-repos/harfbuzz.svg)](https://repology.org/project/harfbuzz/versions)
9[ABI Tracker](http://abi-laboratory.pro/tracker/timeline/harfbuzz/)
10
11This is HarfBuzz, a text shaping library.
12
13For bug reports, mailing list, and other information please visit:
14
15  http://harfbuzz.org/
16
17For license information, see [COPYING](COPYING).
18
19For build information, see [BUILD.md](BUILD.md).
20
21For custom configurations, see [CONFIG.md](CONFIG.md).
22
23For test execution, see [TESTING.md](TESTING.md).
24
25Documentation: https://harfbuzz.github.io
26
27
28<details>
29  <summary>Packaging status of HarfBuzz</summary>
30
31[![Packaging status](https://repology.org/badge/vertical-allrepos/harfbuzz.svg?header=harfbuzz)](https://repology.org/project/harfbuzz/versions)
32
33</details>
34