To enable ST_AsMVT protobuf-c library (for usage) and the protoc-c compiler (for building) are required.
Also, pkg-config is required to verify the correct minimum version of protobuf-c.
See <ulinkurl="https://github.com/protobuf-c/protobuf-c">protobuf-c</ulink>.
To use Wagyu to validate MVT polygons faster, a c++11 compiler is required. It requires <varname>--with-wagyu</varname> to be passed during configure; and it will use CXXFLAGS and the same compiler as the PostgreSQL installation.
By default, Postgis will use Wagyu to validate MVT polygons faster which requires a c++11 compiler. It will use CXXFLAGS and the same compiler as the PostgreSQL installation. To disable this and use GEOS instead use the <varname>--without-wagyu</varname> during the configure step.
</para>
</listitem>
...
...
@@ -599,10 +599,10 @@ tar -xvzf postgis-&last_release_version;.tar.gz</programlisting>
</listitem>
</varlistentry>
<varlistentry>
<term><command>--with-wagyu</command></term>
<term><command>--without-wagyu</command></term>
<listitem>
<para>
When building with MVT support, by default Postgis will use GEOS to clip and validate MVT polygons. You can use <ulinkurl="https://github.com/mapbox/wagyu/">Wagyu</ulink>instead which is faster and guaranteed to produce correct values for this specific case.
When building with MVT support, Postgis will use <ulinkurl="https://github.com/mapbox/wagyu/">Wagyu</ulink>to clip and validate MVT polygons. Wagyu is the fastest alternative and guarantees producing correct values for this specific case, but it requires a C++-11 compiler. With this optional argument you can disable using this library; GEOS will be used instead.