These instructions are based on the generic GNU installation
instructions, but they have been tailored for PSPP. These instructions
-apply only to people wishing to build and install PSPP from source.
+apply only to people wishing to build and install PSPP from source.
Overview
========
tar -xzf pspp-*.tar.gz
cd pspp-*
./configure
- make
+ make
sudo make install
Obviously, you should replace 'pspp-*' in the above, with the name of
-the tarball you are installing.
+the tarball you are installing.
-In 99% of cases, that is all you have to do - FINISHED!
+In 99% of cases, that is all you have to do - FINISHED!
* zlib (http://www.zlib.net/).
- * libxml2 (http://xmlsoft.org/).
+ * libxml2 (http://xmlsoft.org/).
+
+ * metainfo.its, provided by the appstream package. This is required
+ by xgettext version lower then 0.20 to extract the translation
+ strings from the org.fsf.pspp.metainfo.xml.in file. This is only
+ required for building. It is not a runtime requirement.
The following packages are required to enable PSPP's graphing
features. If you cannot arrange to install them, you must run
* GTK+ (http://www.gtk.org/), version 3.22.0 or later.
- * GtkSourceView (http://projects.gnome.org/gtksourceview/)
+ * GtkSourceView (http://projects.gnome.org/gtksourceview/)
version 3.4.0 or later.
* GNU Spread Sheet Widget (http://www.gnu.org/software/ssw)
+ version 0.7 or later.
The following packages are optional:
later. Installing Texinfo will allow you to build PSPP
documentation in PostScript or PDF format.
- * libpq, from Postgresql (http://postgresql.org). This enables PSPP
+ * libpq, from Postgresql (http://postgresql.org). This enables PSPP
to read Postgresql databases. The tests for the Postgresql
interface, but not the Postgresql interface itself, requires the
Postgresql server to be installed.
Basic Installation
==================
-These are installation instructions specific to PSPP (including PSPPIRE,
+These are installation instructions specific to PSPP (including PSPPIRE,
the graphic user interface). These instructions contain the
information most commonly needed by people wishing to build the
program from source. More detailed information can be found in the
./configure CC=c89 CFLAGS=-O0 LIBS=-lposix
+Cross Compiling
+===============
+
To cross-compile PSPP, you will likely need to set the
PKG_CONFIG_LIBDIR environment variable to point to an
appropriate pkg-config for the cross-compilation environment.
+Part of cross-compiling procedure builds a native binary. Therefore, you
+will need not only the dependent libraries for your target, but also for the
+build machine. This is because the native version is used to create
+examples for the user manual.
+
See "Defining Variables", below, for more details.
Installation Names
You can cause programs to be installed with an extra prefix or
suffix on their names by giving `configure' the option
-`--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
+`--program-prefix=PREFIX' or `--program-suffix=SUFFIX'.
Optional Features
=================
Cairo and Pango required to build the GUI, so --without-cairo
implies --without-gui.
-`--with-gui-tools'
- Build the gui developer tools. There is no reason to use this
- option unless you're involved with the development of PSPP
-
`--without-lib{xx}'
Optional libraries should normally be detected and the relevant
functionality will be built they exist. However, on some poorly