[PATCH libinput] doc: extend build instructions for dependencies

[Eric Engestrom]

On Thu, Sep 01, 2016 at 09:53:36AM +1000, Peter Hutterer wrote:
> Signed-off-by: Peter Hutterer <peter.hutterer at who-t.net>
> ---
> Mostly sending this out for any hints on how to deal with this in Arch or
> other distributions not listed here. Let me know and I'll add it to the
> list.

The Arch way would be to install the deps from the PKGBUILD (using the ABS [1]):
	# abs
	$ cd $(mktemp -d)
	$ cp /var/abs/extra/libinput/PKGBUILD .
	$ makepkg --syncdeps --nobuild
but these aren't the simplest instructions...

Cheers,
  Eric

[1] https://wiki.archlinux.org/index.php/Arch_Build_System#Build_package

> 
> Cheers,
>    Peter
> 
>  doc/building.dox | 25 +++++++++++++++++++++----
>  1 file changed, 21 insertions(+), 4 deletions(-)
> 
> diff --git a/doc/building.dox b/doc/building.dox
> index 5b4ca52..a14eba7 100644
> --- a/doc/building.dox
> +++ b/doc/building.dox
> @@ -19,10 +19,27 @@ $> sudo make install
>  @note On Debian-based distributions including Ubuntu and its derivatives skip the
>  ```--libdir=/usr/lib64``` argument.
>  
> -A description on how to fix "No package 'foo' found" errors during the
> -configure stage is available
> -<a href="https://who-t.blogspot.com.au/2014/05/configure-fails-with-no-package-foo.html">in
> -this blog post here</a>.
> +A successful build requires the @ref building_dependencies to be installed
> +at configure time.
> +
> + at subsection building_dependencies Build dependencies
> +
> +libinput has a few build-time dependencies that must be installed prior to
> +running configure. In most cases, it is sufficient to install the
> +dependencies that your distribution uses to build the libinput package.
> +These can be installed with one of the following commands:
> +
> +<ul>
> +<li>Debian/Ubuntu based distributions: ```sudo apt-get build-dep
> +libinput```</li>
> +<li>Fedora 22 and later: ```sudo dnf builddep libinput```</li>
> +<li>SuSE/RHEL/CentOS/Fedora 21 and earlier: ```sudo yum-builddep libinput```</li>
> +</ul>
> +
> +If dependencies are missing, a message ```No package 'foo' found``` will be
> +shown during the configure stage. See
> +<a href="https://who-t.blogspot.com.au/2014/05/configure-fails-with-no-package-foo.html">this blog post here</a>.
> +for instructions on how to fix it.
>  
>  @subsection building_libwacom Building without libwacom
>  
> -- 
> 2.7.4