[pure-lang-svn] SF.net SVN: pure-lang: [249] pure/trunk/INSTALL

[<ag...@us...>]

Revision: 249
          http://pure-lang.svn.sourceforge.net/pure-lang/?rev=249&view=rev
Author:   agraef
Date:     2008-06-16 07:29:41 -0700 (Mon, 16 Jun 2008)

Log Message:
-----------
Update installation instructions.

Modified Paths:
--------------
    pure/trunk/INSTALL

Modified: pure/trunk/INSTALL
===================================================================
--- pure/trunk/INSTALL	2008-06-16 14:00:24 UTC (rev 248)
+++ pure/trunk/INSTALL	2008-06-16 14:29:41 UTC (rev 249)
@@ -25,8 +25,8 @@
 required once. Steps 2-3 can be avoided if binary LLVM packages are available
 for your system. Additional instructions for compiling Pure from SVN sources
 can be found in the INSTALLING FROM SVN SOURCES section below. Moreover, you
-can refer to the OTHER COMPILATION OPTIONS section below for details about
-various options available when building and installing Pure.
+can refer to the OTHER BUILD AND INSTALLATION OPTIONS section below for
+details about various options available when building and installing Pure.
 
 STEP 1. Make sure you have all the necessary dependencies installed (-dev
 denotes corresponding development packages):
@@ -83,9 +83,18 @@
 $ make
 $ sudo make install
 
+The last command installs the pure program, the runtime.h header file, the
+runtime library libpure.so and the library scripts under /usr/local; the
+installation prefix can be changed with the --prefix configure option, see
+OTHER BUILD AND INSTALLATION OPTIONS for details.
+
+(The runtime.h header file is not needed for normal operation, but can be used
+to write C/C++ extensions modules, if you need to access and manipulate Pure
+expressions from C/C++.)
+
 On some systems you may have to tell the dynamic linker to update its cache so
-that it finds the Pure runtime library, libpure.so. E.g., on Linux this can be
-done as follows:
+that it finds the Pure runtime library. E.g., on Linux this can be done as
+follows:
 
 $ sudo /sbin/ldconfig
 
@@ -161,8 +170,8 @@
 $ sudo make install
 
 
-OTHER COMPILATION OPTIONS
-===== =========== =======
+OTHER BUILD AND INSTALLATION OPTIONS
+===== ===== === ============ =======
 
 The Pure configure script takes a few options which enable you to change the
 installation path and control a number of other build options. Moreover, there
@@ -173,10 +182,10 @@
 INSTALLATION PATH
 ------------ ----
 
-By default, the pure program, runtime library and library scripts are
-installed in /usr/local/bin, /usr/local/lib and /usr/local/lib/pure,
-respectively. This can be changed by specifying the desired installation
-prefix with the --prefix option, e.g.:
+By default, the pure program, the runtime.h header file, the runtime library
+and the library scripts are installed in /usr/local/bin, /usr/local/include,
+/usr/local/lib and /usr/local/lib/pure, respectively. This can be changed by
+specifying the desired installation prefix with the --prefix option, e.g.:
 
 $ ./configure --prefix=/usr
 
@@ -195,10 +204,11 @@
 
 Beginning with version 0.4, Pure fully supports parallel installations of
 different versions of the interpreter without any further ado. To these ends,
-bin/pure, lib/libpure.so, lib/pure and man/man1/pure.1 are actually symbolic
-links to the current version (bin/pure-x.y, lib/libpure-x.y.so etc., where x.y
-is the version number). If you install a new version of the interpreter, the
-old version remains available as pure-x.y.
+bin/pure, include/pure, lib/libpure.so, lib/pure and man/man1/pure.1 are
+actually symbolic links to the current version (bin/pure-x.y,
+include/pure-x.y, lib/libpure-x.y.so etc., where x.y is the version
+number). If you install a new version of the interpreter, the old version
+remains available as pure-x.y.
 
 SEPARATE BUILD DIRECTORY
 -------- ----- ---------


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.