When cross-compiling, also build native binaries, and use them to create

[pspp] / INSTALL

diff --git a/INSTALL b/INSTALL
index d565ed4c02023f6e0f14a36a03e072c473e10310..66d9355fced5b9db208e9870653f5fc673c600e2 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -104,6 +104,7 @@ use the GUI, you must run `configure' with --without-gui.
       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:
 
@@ -127,6 +128,10 @@ Other optional packages:
       PSPP to test the Perl module more thoroughly.  It is not needed
       to build or use the Perl module.
 
+    * librsvg enables 300 dpi copy and paste operation. Without librsvg
+      the copy action will only provide images with default resolution
+      which is often 96dpi. This only affects bitmap image formats.
+
 Basic Installation
 ==================
 
@@ -220,10 +225,18 @@ is an example:
 
      ./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