+ 3. You must have pkg-config installed, along with the required library
+ dependencies and ``pc'' files. Look for these packages with your
+ favorite package manager:
+ o boost headers
+ o libpng
+ o libvorbis
+ o Lua
+ o OpenAL
+ o OpenGL (including GLU)
+ o SDL
+ o zlib
+
+ BUILDING
+ Once the build system has been properly configured, it is ready to do
+ some compiling. This is done simply with an invocation of GNU make,
+ perhaps like this:
+
+ make -j2
+
+ Sometimes the command for GNU make is gmake, although it may also be
+ simply make. No other variety of make will work, and you need a fairly
+ recent version of GNU make since some older versions have fatal bugs.
+ The -j flag may be used to perform multiple build steps in parallel,
+ decreasing the amount of time the compile takes on multi-core machines.
+ See make(1) for more information.
+
+ Advanced users may choose to override parts of the configuration with
+ additional arguments to make, although it is rarely useful to do so.
+ However, in the event that some error occurs during the process, it often
+ is useful to retry the make command with the V=1 argument (for verbosity)
+ in order to cause make to echo each actual command before it is executed.
+ Users who are familiar with compiler and linker warnings and errors will
+ then be able diagnose the problem, whether it be a problem with the
+ configuration or something else.
+
+ TESTING
+ After the build process has successfully completed, Yoink should now be
+ able to run from within the build directory, as long as you're not cross-
+ compiling to an incompatible platform. To test this, there is a make
+ target to execute Yoink:
+
+ make run
+
+ If an error occurs and the rest of the build really did complete
+ successfully, the likely problem is that the dynamic libraries could not
+ be found. This may happen if the libraries are installed to a non-
+ standard location, and the linker wasn't given the appropriate -rpath
+ flag. This means that pkg-config failed to provide all of the flags we
+ need. The easiest thing to do in this situation is to reconfigure the
+ build system with the LDFLAGS=-Wl,-rpath=/path/to/lib option set and
+ retry the test (the executable will be rebuilt).
+
+ INSTALLATION
+ Once testing is completed, it is time to copy the Yoink files to their
+ final destinations. As usual, there is a make target to handle the
+ installation:
+
+ make install
+
+ This will cause the files to be copied with the BSD-compatible install
+ program. Of course, you may need to elevate your privileges (i.e. with
+ sudo) if you are installing to a directory your user account does not
+ have write access to.
+
+ The installation destination depends on prefix and other configuration
+ variables. You can override the configuration by passing the arguments
+ directly to make with the install target. The Makefile also supports
+ staging by using the DESTDIR variable passed to make.
+
+ Any failure during installation is probably a result of simply not having
+ sufficient privileges. It will also be a problem if you do not have a
+ BSD-compatible version of install. In the case of the latter, it should
+ be a minor modification to the Makefile to get it working. The build
+ system is still not compatible in many regards.
+
+FILES
+ configure
+ config.h
+ config.mk
+ config.sed
+ Makefile
+ options.lua
+
+SEE ALSO
+ yoinkrc(5), yoink(6)
+
+AUTHORS
+ Charles McGarvey chaz@dogcows.com
+
+NetBSD 5.1.0_PATCH June 13, 2011 NetBSD 5.1.0_PATCH