See Chapter 8.
Start with LibGII - the input handling layer.
LibGGI - the graphics layer - depends on it. Install it second.
After that order is usually not important, except for packages that depends on other packages. This would be documented in the respective README documents.
Check if the input in which make fails should work on your system.
If yes, chances are, that you don't have some development package installed properly. If you can't figure out for yourself, please report to out mailing list metioned in the README. |
If no, just disable it using the --disable flags to configure. You might still want to report that case to the mailinglist. |
Check that you have permissions to read the device /dev/mouse is linked to. PS/2 devices might need read/write access. Your mouse might be misconfigured due to earlier installs or an improperly configured SVGAlib. Please read doc/inputs.txt on how to do it right.
LibGII is rarely used on its own. Most applications will require you to install LibGGI (mind GGI vs. GII !) first. One useful application is delivered with LibGII, though: mhub. See its own manpage for usage information. If you don't know what it is talking about, chances are, that you won't need it.
Commandline switches require application cooperation. LibGII/GGI are intended to give the user full freedom. It allows to override stuff without the application having to care.
Convenience. LibGII is almost always coupled to LibGGI, especially when you need to debug stuff.
GII_INPUT only influences giiOpen() calls with a NULL argument. LibGGI never does this. It determines the required inputlibs and calls LibGII with them in the argument. LibGGI has its own mechanism to add inputs. Have a look at its FAQ or documentation.