The Tor Browser / file comparison
comparison: gfx/harfbuzz/README-mozilla
gfx/harfbuzz/README-mozilla
- branch
- TOR_BUG_9701
- changeset 14
- 925c144e1f1f
equal
deleted
inserted
replaced
| -1:000000000000 | 0:2b05142a6bf0 |
|---|---|
| 1 gfx/harfbuzz status as of 2012-08-16: | |
| 2 | |
| 3 This directory contains the "harfbuzz-ng" source from the 'master' branch of | |
| 4 git://anongit.freedesktop.org/git/harfbuzz. | |
| 5 | |
| 6 UPDATING: | |
| 7 | |
| 8 Note that hb-ot-shape-complex-indic-machine.hh and gfx/harfbuzz/src/hb-version.h | |
| 9 are not present in the upstream Git repository. These are created at build time | |
| 10 by the harfbuzz build system; but as we don't use that build system in mozilla, | |
| 11 it is necessary to refresh these files when updating harfbuzz, and check them in | |
| 12 to the mozilla tree. (This avoids adding the ragel processor to mozilla's build | |
| 13 prerequisites.) | |
| 14 | |
| 15 The normal approach to updating harfbuzz, therefore, is to pull the latest HB | |
| 16 source into a scratch directory and do a local build; then copy the original | |
| 17 sources AND the generated headers mentioned above from the build directory into | |
| 18 the mozilla tree. | |
| 19 | |
| 20 In addition, the src/Makefile.in file here is NOT from upstream, nor is it | |
| 21 generated from src/Makefile.am (the original harfbuzz version); it is a mozilla- | |
| 22 specific makefile that is maintained by hand. It should only need updating when | |
| 23 new source files or exported headers are added in harfbuzz. |
