Fix drawing of labels in insets

[lyx.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index af7578d82ce4c4ab93af48a401a9561da7bd51f7..99114b2de356456c65330ed9caf3d0a1a2ccc27c 100644 (file)
--- a/INSTALL
+++ b/INSTALL
@@ -6,7 +6,7 @@ Quick compilation guide
 
 These four steps will compile, test and install LyX:
 
 
 These four steps will compile, test and install LyX:
 

-       0) Linux users beware: You need qt4 and qt4-devel packages
+       0) Linux users beware: You need qt4/5 and qt4/5-devel packages

           of the same version to compile LyX.
 
           In general, it is also recommended to have pkg-config
           of the same version to compile LyX.
 
           In general, it is also recommended to have pkg-config


@@ -18,6 +18,7 @@ These four steps will compile, test and install LyX:
           (for example, "--with-qt-dir=/usr/share/qt4/") if the
           environment variable QTDIR is not set and pkg-config is not
           available.
           (for example, "--with-qt-dir=/usr/share/qt4/") if the
           environment variable QTDIR is not set and pkg-config is not
           available.

+          You will need --enable-qt5 switch for choosing qt5 over qt4.

 
           See Note below if ./configure script is not present.
 
 
           See Note below if ./configure script is not present.
 


@@ -36,8 +37,8 @@ Note for Git checkouts
 -----------------------------
 
 If you have checked this out from Git, you need to have:
 -----------------------------
 
 If you have checked this out from Git, you need to have:

-* automake (supported versions are 1.8--1.15)
-* autoconf (supported versions are 2.60--2.69)
+* automake (supported versions are 1.14--1.16)
+* autoconf (supported versions are 2.65--2.69)

 Then type "./autogen.sh" to build the needed configuration
 files and proceed as stated above/below.
 
 Then type "./autogen.sh" to build the needed configuration
 files and proceed as stated above/below.
 


@@ -49,18 +50,17 @@ Requirements
 
 First of all, you will need a recent C++ compiler, where recent means
 that the compilers are close to C++11 standard conforming like gcc (at
 
 First of all, you will need a recent C++ compiler, where recent means
 that the compilers are close to C++11 standard conforming like gcc (at

-least 4.3) or clang.
+least 4.6) or clang.

 
 LyX makes great use of the 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 of LyX.
 
 
 LyX makes great use of the 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 of LyX.
 

-For full LyX usability we suggest to use Qt 5.x and Qt 5.6 and higher,
-or at the very least Qt 5.4. For compilation you need to compile against
-at least Qt 4.8 which has been widely tested, and for Windows we advise
-at least Qt 4.8.4. For Qt 5 we recommend at least Qt 5.4. The only
-special point to make is that you must ensure that both LyX and the Qt
-libraries are compiled with the same C++ compiler.
+For full LyX usability we suggest to use Qt 5.6 and higher, or at the
+very least Qt 5.4. For compilation you need to compile against at least
+Qt 4.8 which has been widely tested, and for Windows we advise at least
+Qt 4.8.4. The only special point to make is that you must ensure that
+both LyX and the Qt libraries are compiled with the same C++ compiler.

 
 To build LyX with spell checking capabilities included you have to
 install at least one of the development packages of the spell checker
 
 To build LyX with spell checking capabilities included you have to
 install at least one of the development packages of the spell checker


@@ -228,6 +228,9 @@ The following options allow you to tweak the generated code more precisely (see
     --without-included-boost is specified). You may have to use
     --disable-stdlib-debug when linking development versions against
     your system's boost library.
     --without-included-boost is specified). You may have to use
     --disable-stdlib-debug when linking development versions against
     your system's boost library.

+    The same problem applies to hunspell (as of hunspell 1.5). So either
+    compile --with-included-hunspell or --disable-stdlib-debug when
+    linking development versions against your system's hunspell library.

 
   o --enable-monolithic-build[=boost,client,insets,mathed,core,tex2lyx,frontend-qt4]
     that enables monolithic build of the given parts of the source
 
   o --enable-monolithic-build[=boost,client,insets,mathed,core,tex2lyx,frontend-qt4]
     that enables monolithic build of the given parts of the source