fix to the lyxstring bug, better searching for dep files in latex log, use \hfil...

[lyx.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index f3136328a4270659d308a8ca92190f84d0be92c9..969b86571a208aa9f5d5b3ee5aa3ac507548009c 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -34,8 +34,8 @@ You will need to have both an Xforms library and Xpm library to compile
 LyX.  It is imperative that you have the correct versions of these 
 libraries, and their associated header files.
 
-As of LyX version 1.1.1, you will need to have Xforms library and header
-version 0.81, 0.86, or 0.88.  Version 0.88 is a stable release and the
+As of LyX version 1.1.5, you will need to have Xforms library and header
+version 0.88 or 0.89.  Version 0.88 is a stable release and the
 recommended version.  On some systems, such as linux ELF, there are shared 
 library versions of the Xforms library, which require an installation step 
 to configure the system.
@@ -44,8 +44,8 @@ Xforms is available (free) only in binary format, source code is not
 available.  If it is not available for your machine, contact the Xforms
 developers to request a version for your system.  You can get it from
 
-    http://bragg.phys.uwm.edu/xforms
-    ftp://bragg.phys.uwm.edu/pub/xforms/
+    http://world.std.com/~xforms/
+    ftp://ncmir.ucsd.edu/pub/xforms/
     ftp://ftp.lyx.org/pub/xforms/
     ftp://ftp.fu-berlin.de/unix/X11/gui/xforms
     ftp://ftp.cs.ruu.nl/pub/XFORMS/
@@ -58,10 +58,16 @@ libXpm can be found at:
            (or similar locations at other sunsites like sunsite.unc.edu)
 
 You will also need a recent C++ compiler, where recent means that the
-compilers knows a bit about the C++ standard. Compilers that are known
-to compile LyX are gcc 2.8.1 and 2.95.x, the various versions of egcs
-and Digital C++ version 6.1. Please tell us your experience with other
-compilers. 
+compilers are close to C++ standard conforming. Compilers that are
+known to compile LyX are gcc 2.8.1 and 2.95.x, the various versions of
+egcs and Digital C++ version 6.1. Please tell us your experience with
+other compilers. It is _not_ possible to compile LyX with gcc 2.7.x,
+and this is not likely to change in the future.
+
+Note that, contrary to LyX 1.0.x, LyX 1.1.x makes great use of C++
+Standard Template Library (STL); this means that gcc users will have
+to install the relevant libstdc++ library to be able to compile this
+version.
 
 If you make modifications to files in src/ (for example by applying a 
 patch), you will need to have the GNU gettext package installed, due to 
@@ -113,7 +119,12 @@ flags:
 
   o --with-extra-prefix[=DIRECTORY] that is equivalent to
        --with-extra-lib=DIRECTORY/lib --with-extra-inc=DIRECTORY/include
-   If DIRECTORY is not specified, the current prefix is used.
+    If DIRECTORY is not specified, the current prefix is used.
+
+  o --with-lyxname=STRING sets the name of the installed LyX binary and 
+    of the LyX library directory to STRING. This may be used to
+    compile lyx as lyx-1.1 and avoid clashes with earlier/later
+    versions. Default is "lyx". 
 
   o --with-two-colors=[yes|no] that forces LyX to use two colors pixmaps
     (bitmaps) instead of the full-colored standard ones.  Defaults to no.
@@ -145,10 +156,6 @@ Moreover, the following generic configure flags may be useful:
     installation. [defaults to where lyx has already been installed or
     /usr/local]
 
-  o --program-suffix=STRING sets the name of the installed LyX binary and 
-      of the LyX library directory to lyxSTRING. This may be used to
-      compile lyx as lyx-1.0.0 and avoid clashes with earlier/later versions.
-
   o --datadir=DIRECTORY gives the directory where all extra LyX 
     files (lyxrc example, documentation, templates and layouts
     definitions) will be installed. 
@@ -184,7 +191,7 @@ desperate cases:
     this flag is on for development versions only.
 
   o --enable-assertions that make the compilier generater run-time
-    code which checks that some variables have sane values.  Opposite
+    code which checks that some variables have sane values. Opposite
     is --disable-assertions.  By default, this flag is on for
     development versions only.