Ignore:
Timestamp:
06/19/2015 07:25:49 PM (6 years ago)
Author:
Bruce Dubbs <bdubbs@…>
Branches:
10.0, 10.1, 11.0, 7.10, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, lazarus, nosym, perl-modules, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
06da9a6
Parents:
a5a776af
Message:

Simplify qt4 and qt5 install instructions.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@16141 af4574ff-66df-0310-9fd7-8a98e5e911e0

File:
1 edited

Legend:

Unmodified
Added
Removed
  • xincludes/qt-alternatives.xml

    ra5a776af r0dd2bc6  
    2727    install the components in the several directories of the <filename
    2828    class='directory'>/usr</filename> hierarchy or install the
    29     entire package in a separate directory of your choice. We
     29    entire package in a separate directory of your choice. <!-- We
    3030    refer to these options below as "Method 1: Installing in /usr"
    31     and "Method 2: Installing in /opt".</para>
     31    and "Method 2: Installing in /opt". --></para>
    3232
    3333    <para>If both versions of Qt are to be installed, one or both versions need
     
    5151
    5252    <para> The advantage of installing <application>Qt</application> in a
    53     custom directory such as
    54     <filename class='directory'>/opt/qt-&qt4-version;</filename> or
    55     <filename class='directory'>/opt/qt-&qt5-version;</filename> or
    56     is that it keeps all the
    57     package files consolidated in a dedicated directory hierarchy. By using
     53    custom directory such as <filename
     54    class='directory'>/opt/qt-&qt4-version;</filename> or <filename
     55    class='directory'>/opt/qt-&qt5-version;</filename> is that it keeps all
     56    the package files consolidated in a dedicated directory hierarchy. By using
    5857    this method, an update can be made without overwriting a previous
    5958    installation and users can easily revert to a previous version by changing
Note: See TracChangeset for help on using the changeset viewer.