mirror of
https://github.com/Sneed-Group/Poodletooth-iLand
synced 2024-12-26 21:22:27 -06:00
69 lines
2.9 KiB
Text
69 lines
2.9 KiB
Text
|
///////////////////////////////////////////////////////////////////////
|
||
|
|
// Caution: there are two separate, independent build systems:
|
||
|
|
// 'makepanda', and 'ppremake'. Use one or the other, do not attempt
|
||
|
|
// to use both. This file is part of the 'ppremake' system.
|
||
|
|
///////////////////////////////////////////////////////////////////////
|
||
|
|
|
||
|
|
To build ppremake on Unix (or Windows Cygwin) using autoconf, follow
|
||
|
|
the following steps.
|
||
|
|
|
||
|
|
If you are on Windows, note that you may build ppremake either using
|
||
|
|
or without using Cygwin. This document describes how to build it with
|
||
|
|
Cygwin; if you want to build it without Cygwin just use the provided
|
||
|
|
VC7 project file. However, if you intend to use Cygwin to build and
|
||
|
|
install the rest of Panda (see the top-level INSTALL document for
|
||
|
|
Panda), you must also use Cygwin to build ppremake, since otherwise
|
||
|
|
ppremake will not be able to correctly decode Cygwin-style pathnames
|
||
|
|
into Windows-style pathnames. In general, if you have Cygwin
|
||
|
|
installed, you should follow these steps to build ppremake; you should
|
||
|
|
use the VC7 project files only if you don't have Cygwin and you have
|
||
|
|
no intention of getting it.
|
||
|
|
|
||
|
|
(1) If the file "configure" exists, skip to step (4), below. This is
|
||
|
|
the normal case; you must have unpacked an archive file that
|
||
|
|
includes the normal autoconf files already generated for you. You
|
||
|
|
can now successfully build the tree without having autoconf
|
||
|
|
installed on your own machine.
|
||
|
|
|
||
|
|
Otherwise, you must have checked this tree directly out from CVS.
|
||
|
|
Since the autoconf-generated files are not part of the source
|
||
|
|
tree, you must now generate them.
|
||
|
|
|
||
|
|
(2) Install autoconf and/or automake, if they are not already
|
||
|
|
installed. If you are building on a Linux machine, you probably
|
||
|
|
already have these installed. If you are running on Cygwin, you
|
||
|
|
may need to re-run the Cygwin install program and explicitly
|
||
|
|
check the "autoconf" option in order to install these scripts.
|
||
|
|
Also, if you are on Cygwin, you will need to ensure that gcc is
|
||
|
|
installed.
|
||
|
|
|
||
|
|
(3) Run the following commands within the ppremake directory, in
|
||
|
|
order:
|
||
|
|
|
||
|
|
aclocal
|
||
|
|
autoheader
|
||
|
|
automake --foreign -a
|
||
|
|
autoconf
|
||
|
|
|
||
|
|
(4) Now you have a tree that has been processed with autoconf, and you
|
||
|
|
are ready to run the resulting configure script. Type the
|
||
|
|
following command within the ppremake directory:
|
||
|
|
|
||
|
|
./configure
|
||
|
|
|
||
|
|
This will examine the machine's environment for header files,
|
||
|
|
etc., and set up the Makefile to build ppremake appropriately.
|
||
|
|
The default path to copy the installed binary is within
|
||
|
|
/usr/local/panda; if you wish to install it somewhere else, for
|
||
|
|
instance /my/install/dir, use:
|
||
|
|
|
||
|
|
./configure --prefix=/my/install/dir
|
||
|
|
|
||
|
|
Note that this is a Cygwin-style path, with forward slashes and no
|
||
|
|
drive letter; not a Windows-style path.
|
||
|
|
|
||
|
|
(5) Type the following to build and install ppremake:
|
||
|
|
|
||
|
|
make
|
||
|
|
make install
|