[doc] add a note for packagers
This commit is contained in:
parent
0fc52d3b2d
commit
28554cb831
8
BUILD.md
8
BUILD.md
|
@ -13,7 +13,13 @@ and on ArchLinux and Manjaro:
|
||||||
|
|
||||||
then use meson to build the project like `meson build && meson test -Cbuild`.
|
then use meson to build the project like `meson build && meson test -Cbuild`.
|
||||||
|
|
||||||
On macOS, `brew install pkg-config ragel gtk-doc freetype glib cairo meson` then use meson like above.
|
On macOS, `brew install pkg-config ragel gtk-doc freetype glib cairo meson` then use
|
||||||
|
meson like above.
|
||||||
|
|
||||||
On Windows, meson builds the project like above if a working MSVC's cl.exe (`vcvarsall.bat`)
|
On Windows, meson builds the project like above if a working MSVC's cl.exe (`vcvarsall.bat`)
|
||||||
or gcc/clang is already on your path, it fetches and compiles most of the dependencies also.
|
or gcc/clang is already on your path, it fetches and compiles most of the dependencies also.
|
||||||
|
|
||||||
|
Linux packagers are advised to at least use `--buildtype=release -Dauto_features=enabled --wrap-mode=nodownload`
|
||||||
|
and install any other needed packages (most distributions build harfbuzz with
|
||||||
|
graphite support which needed to enabled separately, `-Dgraphite=enabled`),
|
||||||
|
and follow other best practices of packaging a meson project.
|
||||||
|
|
Loading…
Reference in New Issue