meson.html 6.75 KB
Newer Older
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=utf-8">
  <title>Compilation and Installation using Meson</title>
  <link rel="stylesheet" type="text/css" href="mesa.css">
</head>
<body>

<div class="header">
  <h1>The Mesa 3D Graphics Library</h1>
</div>

<iframe src="contents.html"></iframe>
<div class="content">

<h1>Compilation and Installation using Meson</h1>

<h2 id="basic">1. Basic Usage</h2>

21 22
<p><strong>The Meson build system is generally considered stable and ready
for production</strong></p>
23

24 25
<p>The meson build is tested on Linux, macOS, Cygwin and Haiku, FreeBSD,
DragonflyBSD, NetBSD, and should work on OpenBSD.</p>
26

27
<p><strong>Mesa requires Meson >= 0.45.0 to build.</strong>
28 29 30 31

Some older versions of meson do not check that they are too old and will error
out in odd ways.
</p>
32 33 34 35

<p>
The meson program is used to configure the source directory and generates
either a ninja build file or Visual Studio® build files. The latter must
36
be enabled via the <code>--backend</code> switch, as ninja is the default backend on all
37 38 39 40 41 42 43 44 45 46 47 48 49 50 51
operating systems. Meson only supports out-of-tree builds, and must be passed a
directory to put built and generated sources into. We'll call that directory
"build" for examples.
</p>

<pre>
    meson build/
</pre>

<p>
To see a description of your options you can run <code>meson configure</code>
along with a build directory to view the selected options for. This will show
your meson global arguments and project arguments, along with their defaults
and your local settings.

52
Meson does not currently support listing options before configure a build
53 54 55 56 57 58 59 60 61 62
directory, but this feature is being discussed upstream.
</p>

<pre>
    meson configure build/
</pre>

<p>
With additional arguments <code>meson configure</code> is used to change
options on already configured build directory. All options passed to this
63
command are in the form <code>-D "command"="value"</code>.
64 65 66 67 68 69
</p>

<pre>
    meson configure build/ -Dprefix=/tmp/install -Dglx=true
</pre>

70 71 72 73 74 75 76 77
<p>
Note that options taking lists (such as <code>platforms</code>) are
<a href="http://mesonbuild.com/Build-options.html#using-build-options">a bit
more complicated</a>, but the simplest form compatible with Mesa options
is to use a comma to separate values (<code>-D platforms=drm,wayland</code>)
and brackets to represent an empty list (<code>-D platforms=[]</code>).
</p>

78 79 80 81 82 83 84 85 86 87 88 89 90 91 92
<p>
Once you've run the initial <code>meson</code> command successfully you can use
your configured backend to build the project. With ninja, the -C option can be
be used to point at a directory to build.
</p>

<pre>
    ninja -C build/
</pre>

<p>
Without arguments, it will produce libGL.so and/or several other libraries
depending on the options you have chosen. Later, if you want to rebuild for a
different configuration, you should run <code>ninja clean</code> before
changing the configuration, or create a new out of tree build directory for
93 94 95
each configuration you want to build
<a href="http://mesonbuild.com/Using-multiple-build-directories.html">as
recommended in the documentation</a>
96 97
</p>

98 99 100 101 102 103 104
<p>
Autotools automatically updates translation files as part of the build process,
meson does not do this. Instead if you want translated drirc files you will need 
to invoke non-default targets for ninja to update them:
<code>ninja -C build/ xmlpool-pot xmlpool-update-po xmlpool-gmo</code>
</p>

105
<dl>
106
<dt><code>Environment Variables</code></dt>
107
<dd><p>Meson supports the standard CC and CXX environment variables for
108
changing the default compiler, and CFLAGS, CXXFLAGS, and LDFLAGS for setting
109
options to the compiler and linker during the initial configuration.
110

111 112 113 114 115
These arguments are consumed and stored by meson when it is initialized. To
change these flags after the build is initialized (or when doing a first
initialization), consider using <code>-D${lang}_args</code> and
<code>-D${lang}_link_args</code> instead. Meson will never change compiler in a
configured build directory.
116 117 118 119 120 121
</p>

<pre>
    CC=clang CXX=clang++ meson build-clang
    ninja -C build-clang
    ninja -C build-clang clean
122 123
    meson configure build -Dc_args="-Wno-typedef-redefinition"
    ninja -C build-clang
124 125
</pre>

126 127 128 129 130 131
<p>
The default compilers depends on your operating system. Meson supports most of
the popular compilers, a complete list is available
<a href="http://mesonbuild.com/Reference-tables.html#compiler-ids">here</a>.
</p>

132
<p>Meson also honors <code>DESTDIR</code> for installs</p>
133 134 135 136
</dd>


<dt><code>LLVM</code></dt>
137
<dd><p>Meson includes upstream logic to wrap llvm-config using its standard
138
dependency interface. It will search <code>$PATH</code> (or <code>%PATH%</code> on windows) for
139 140
llvm-config (and llvm-config$version and llvm-config-$version), so using an
LLVM from a non-standard path is as easy as
141 142 143 144
<code>PATH=/path/with/llvm-config:$PATH meson build</code>.
</p></dd>
</dl>

145
<dl>
146 147 148
<dt><code>PKG_CONFIG_PATH</code></dt>
<dd><p>The
<code>pkg-config</code> utility is a hard requirement for configuring and
149 150 151 152 153
building Mesa on Unix-like systems. It is used to search for external libraries
on the system. This environment variable is used to control the search path for
<code>pkg-config</code>. For instance, setting
<code>PKG_CONFIG_PATH=/usr/X11R6/lib/pkgconfig</code> will search for package
metadata in <code>/usr/X11R6</code> before the standard directories.</p>
154 155 156 157 158 159 160 161
</dd>
</dl>

<p>
One of the oddities of meson is that some options are different when passed to
the <code>meson</code> than to <code>meson configure</code>. These options are
passed as --option=foo to <code>meson</code>, but -Doption=foo to <code>meson
configure</code>. Mesa defined options are always passed as -Doption=foo.
162
</p>
163 164 165 166 167 168 169 170

<p>For those coming from autotools be aware of the following:</p>

<dl>
<dt><code>--buildtype/-Dbuildtype</code></dt>
<dd><p>This option will set the compiler debug/optimisation levels to aid
debugging the Mesa libraries.</p>

171 172 173 174
<p>Note that in meson this defaults to <code>debugoptimized</code>, and
not setting it to <code>release</code> will yield non-optimal
performance and binary size. Not using <code>debug</code> may interfere
with debugging as some code and validation will be optimized away.
175 176
</p>

177
<p> For those wishing to pass their own optimization flags, use the <code>plain</code>
178 179
buildtype, which causes meson to inject no additional compiler arguments, only
those in the C/CXXFLAGS and those that mesa itself defines.</p>
180 181 182 183 184
</dd>
</dl>

<dl>
<dt><code>-Db_ndebug</code></dt>
185
<dd><p>This option controls assertions in meson projects. When set to <code>false</code>
186 187 188 189 190 191
(the default) assertions are enabled, when set to true they are disabled. This
is unrelated to the <code>buildtype</code>; setting the latter to
<code>release</code> will not turn off assertions.
</p>
</dd>
</dl>
192 193 194 195

</div>
</body>
</html>