docs/html/install-harfbuzz.html

   1 <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
   2 <html>
   3 <head>
   4 <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
   5 <title>Installing HarfBuzz: HarfBuzz Manual</title>
   6 <meta name="generator" content="DocBook XSL Stylesheets V1.79.1">
   7 <link rel="home" href="index.html" title="HarfBuzz Manual">
   8 <link rel="up" href="pt01.html" title="Part I. User's manual">
   9 <link rel="prev" href="why-is-it-called-harfbuzz.html" title="Why is it called HarfBuzz?">
  10 <link rel="next" href="building.html" title="Building HarfBuzz">
  11 <meta name="generator" content="GTK-Doc V1.25 (XML mode)">
  12 <link rel="stylesheet" href="style.css" type="text/css">
  13 </head>
  14 <body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
  15 <table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="5"><tr valign="middle">
  16 <td width="100%" align="left" class="shortcuts"></td>
  17 <td><a accesskey="h" href="index.html"><img src="home.png" width="16" height="16" border="0" alt="Home"></a></td>
  18 <td><a accesskey="u" href="pt01.html"><img src="up.png" width="16" height="16" border="0" alt="Up"></a></td>
  19 <td><a accesskey="p" href="why-is-it-called-harfbuzz.html"><img src="left.png" width="16" height="16" border="0" alt="Prev"></a></td>
  20 <td><a accesskey="n" href="building.html"><img src="right.png" width="16" height="16" border="0" alt="Next"></a></td>
  21 </tr></table>
  22 <div class="chapter">
  23 <div class="titlepage"><div><div><h2 class="title">
  24 <a name="install-harfbuzz"></a>Installing HarfBuzz</h2></div></div></div>
  25 <div class="toc"><dl class="toc">
  26 <dt><span class="section"><a href="install-harfbuzz.html#download">Downloading HarfBuzz</a></span></dt>
  27 <dt><span class="section"><a href="building.html">Building HarfBuzz</a></span></dt>
  28 <dd><dl>
  29 <dt><span class="section"><a href="building.html#building.linux">Building on Linux</a></span></dt>
  30 <dt><span class="section"><a href="building.html#building.windows">Building on Windows</a></span></dt>
  31 <dt><span class="section"><a href="building.html#building.macos">Building on macOS</a></span></dt>
  32 <dt><span class="section"><a href="building.html#configuration">Configuration options</a></span></dt>
  33 </dl></dd>
  34 </dl></div>
  35 <div class="section">
  36 <div class="titlepage"><div><div><h2 class="title" style="clear: both">
  37 <a name="download"></a>Downloading HarfBuzz</h2></div></div></div>
  38 <p>
  39       The HarfBuzz source code is hosted at <a class="ulink" href="https://github.com/harfbuzz/harfbuzz" target="_top">github.com/harfbuzz/harfbuzz</a>. The
  40       same source tree is also available at the
  41       <a class="ulink" href="http://cgit.freedesktop.org/harfbuzz/" target="_top">Freedesktop.org</a>
  42       site.
  43     </p>
  44 <p>
  45       Tarball releases and Win32 binary bundles (which include the
  46       libharfbuzz DLL, hb-view.exe, hb-shape.exe, and all
  47       dependencies) of HarfBuzz can be downloaded from <a class="ulink" href="https://github.com/harfbuzz/harfbuzz" target="_top">github.com/harfbuzz/harfbuzz/releases</a>
  48       or from
  49       <a class="ulink" href="http://www.freedesktop.org/software/harfbuzz/release/" target="_top">Freedesktop.org</a>.
  50     </p>
  51 <p>
  52       Release notes are posted with each new release to provide an
  53       overview of the changes. The project <a class="ulink" href="https://github.com/harfbuzz/harfbuzz/issues" target="_top">tracks bug
  54       reports and other issues</a> on GitHub. Discussion and
  55       questions are welcome on the <a class="ulink" href="http://freedesktop.org/mailman/listinfo/harfbuzz/" target="_top">HarfBuzz
  56       mailing list</a>.
  57     </p>
  58 <p>
  59       The API included in the <code class="filename">hb.h</code> file will not change in a
  60       compatibility-breaking way in any release. However, other,
  61       peripheral headers are more likely to go through minor
  62       modifications. We will do our best to never change APIs in an
  63       incompatible way. We will <span class="emphasis"><em>never</em></span> break the ABI.
  64     </p>
  65 </div>
  66 </div>
  67 <div class="footer">
  68 <hr>Generated by GTK-Doc V1.25</div>
  69 </body>
  70 </html>