* libtool 1.5.22 (or later).
- * Texinfo 4.7 or later, to build the documentation.
+ * Texinfo 5.2 or later, to build the documentation.
+
+ * Gimp -- 2.8.2 is known to work
After you install PSPP's prerequisites, you must obtain a copy of
Gnulib, then bootstrap the tree, as described in the sections below.
Gnulib does not maintain a stable API or ABI, so it is possible that
PSPP will not work with older or newer versions of Gnulib.
- commit 0883405cc751858a633bebc56acb75381a6e50c8
- Author: Eric Blake <ebb9@byu.net>
- Date: Wed Nov 18 06:59:44 2009 -0700
+ commit 418a494eaac2dbec290de5991059bc9b33dc7df1
+ Author: John E. Malmberg <wb8tyw@gmail.com>
+ Date: Sat Jul 15 23:11:44 2017 +0200
- utimens: fix regression on Solaris
+ sys_socket: Add support for OpenVMS.
+ * lib/sys_socket.in.h [__VMS]: Define CMSG_SPACE, CMSG_LEN.
+ * doc/posix-headers/sys_socket.texi: Mention OpenVMS issues.
To clone Gnulib into a directory named "gnulib" using Git, and then
check out this particular commit, run these commands:
make check
or for a more thorough test:
make distcheck
+
+Glade UI Design
+---------------
+
+The ui files in src/ui/gui may be viewed (maybe changed) with Glade. For this
+you need
+
+ * libgladeui 2.0 or later
+
+Then you need to run
+
+ configure --with-gui-tools
+ make
+ make install
+
+psppire uses some self defined widgets. To use glade these widgets have
+to be announced to glade such that you can view the interface.
+The install process will install the psppire glade library, icons and
+psppire.xml files in the appropriate system locations. You cannot override
+this with --prefix. After that you can run "glade" and open the ui files.
+
+Building from git on Mac OS
+---------------------------
+
+You can build on MacOS in the macports environment. After installing all
+required packages to resolve library dependencies and autotools e.t.c, you
+run make -f Smake as described above.
+
+The macports system provides the libraries and header files in a separate
+location from the MacOS system libraries. The typical locations are
+
+Libraries: /opt/local/lib
+Headers: /opt/local/include
+
+pspp under macports will be linked against the macports libraries. The configure
+script has to be informed about the library and header locations. Assume the following
+directory structure for an out of tree build:
+
+~/mypspp
+ |----pspp (This is the pspp git directory)
+ |----install (The install location containing also ui files for psppire)
+ |----build (The build directory)
+ |----gnulib (The gnulib directory as described above)
+
+Then you can build with the following commands:
+
+ cd ~/mypspp/pspp
+ make -f Smake
+ cd ../build
+ ../pspp/configure --prefix=/Users/USER/mypspp/install \
+ LDFLAGS=-L/opt/local/lib \
+ CPPFLAGS=-I/opt/local/include
+ make
+ make install
+ ../install/bin/psppire (If everything worked, you should see psppire...)