The quick and dirty instructions: ./configure make && make install The longer, more detailed instructions: 1. Run ./configure --help to see how you can customize the installation. If this step fails, you probably don't have Lua installed. Lua is required to configure the build system. It is also required by the built product. 2. Run ./configure with whatever options you like. Use --prefix to set the directory where Yoink will be installed. Use --datadir to set the directory where the resource files will be installed. Use --host if you want to cross-compile for another type of system--you will need a working cross-compiler toolchain installed. Use CC and CXX to set the C and C++ compiler commands, respectively. Use CFLAGS and LDFLAGS to set the compiler and linker flags, respectively. If this step fails, make sure you have a working toolchain (including compilers and archivers). Also make sure you have the required libraries. You also need pkg-config and all the relevant ``pc'' files for each library dependency. 3. Run make. If you have a multi-core or multi-processor system, you may also want to use the -j option to perform compilations in parallel. See make(1) for more information. If this step fails, you may need to change your configuration from step 2 and try again. In particular, you may need to change the CFLAGS and LDFLAGS, depending on whether it is the compiler that has a problem or the linker. 4. Run make run to run the program without installing. If this step fails, either step 3 didn't actually complete successfully, or there is a bug in the code that is revealed on your platform. You may also need to modify LDFLAGS in step 2 and try again, making sure to set the correct rpath so that the shared libraries will be found at runtime. Note that the linker will be invoked through the compiler. 5. Run make install to copy the files into the installation directories you have specified in step 2. You're done! If this step fails, you probably do not have correct filesystem permissions to install to your chosen directory. Either do the install with elevated privileges, or start at step 2 again and specify --prefix with some directory that you have write access to, such as $HOME/usr.