Dogcows Code - chaz/yoink/blob - INSTALL

   1
   2 The quick and dirty instructions:
   3
   4  ./configure
   5  make && make install
   6
   7
   8 The longer, more detailed instructions:
   9
  10 1. Run ./configure --help to see how you can customize the installation.
  11
  12    If this step fails, you probably don't have Lua installed.  Lua is
  13    required to configure the build system.  It is also required by the
  14    built product.
  15
  16 2. Run ./configure with whatever options you like.  Use --prefix to set the
  17    directory where Yoink will be installed.  Use --datadir to set the
  18    directory where the resource files will be installed.  Use --host if you
  19    want to cross-compile for another type of system--you will need a
  20    working cross-compiler toolchain installed.  Use CC and CXX to set the C
  21    and C++ compiler commands, respectively.  Use CFLAGS and LDFLAGS to
  22    set the compiler and linker flags, respectively.
  23
  24    If this step fails, make sure you have a working toolchain (including
  25    compilers and archivers).  Also make sure you have the required
  26    libraries.  You also need pkg-config and all the relevant ``pc'' files
  27    for each library dependency.
  28
  29 3. Run make.  If you have a multi-core or multi-processor system, you may
  30    also want to use the -j option to perform compilations in parallel.  See
  31    make(1) for more information.
  32
  33    If this step fails, you may need to change your configuration from step
  34    2 and try again.  In particular, you may need to change the CFLAGS and
  35    LDFLAGS, depending on whether it is the compiler that has a problem or
  36    the linker.
  37
  38 4. Run make run to run the program without installing.
  39
  40    If this step fails, either step 3 didn't actually complete successfully,
  41    or there is a bug in the code that is revealed on your platform.  You
  42    may also need to modify LDFLAGS in step 2 and try again, making sure to
  43    set the correct rpath so that the shared libraries will be found at
  44    runtime.  Note that the linker will be invoked through the compiler.
  45
  46 5. Run make install to copy the files into the installation directories you
  47    have specified in step 2.  You're done!
  48
  49    If this step fails, you probably do not have correct filesystem
  50    permissions to install to your chosen directory.  Either do the install
  51    with elevated privileges, or start at step 2 again and specify --prefix
  52    with some directory that you have write access to, such as $HOME/usr.
  53