source: xincludes/qt-alternatives.xml@ ec7940be

10.0 10.1 11.0 11.1 11.2 11.3 7.10 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 ken/inkscape-core-mods krejzi/svn lazarus nosym perl-modules plabs/python-mods qt5new systemd-11177 systemd-13485 trunk upgradedb xry111/intltool xry111/soup3 xry111/test-20220226
Last change on this file since ec7940be was ec7940be, checked in by Bruce Dubbs <bdubbs@…>, 9 years ago

Rewrite Qt pages
Add corrections for some paths (e.g. man pages)

git-svn-id: svn:// af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 3.3 KB
1<?xml version="1.0" encoding="ISO-8859-1"?>
2<!DOCTYPE note PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "" [
4 <!ENTITY % general-entities SYSTEM "../general.ent">
5 %general-entities;
8<!-- $LastChangedBy: $
9 $Date: $ -->
12 <title>Qt Installation Alternatives</title>
14 <para>The installation of <application>Qt</application> presents
15 several challenges and choices. Complicating the Qt installation is the fact
16 that there are two versions, <application>Qt4</application> and
17 <application>Qt5</application>, that have executable programs with
18 identical names. If both packages are installed on one system,
19 the only methods to manage which set of programs is used is to
20 either control the users' <envar>PATH</envar> or to rename files
21 either directly or via symbolic links. Both packages cannot
22 be installed in the same directory.
23 </para>
25 <para>If you are only going to install one of the Qt versions,
26 the choice of installation methods is easier. You can either
27 install the components in the several directories of the <filename
28 class='directory'>/usr</filename> hierarchy or install the
29 entire package in a separate directory of your choice. We
30 refer to these options below as "Method 1: Installing in /usr"
31 and "Method 2: Installing in /opt".</para>
33 <para>If both versions of Qt are to be installed, one or both versions need
34 to be installed in a separate directory. For the purposes here we use the
35 <filename class='directory'>/opt</filename> directory. The selection of
36 which version is being used by individual users on a system is controlled
37 by the <envar>PATH</envar> variable. Other systems can be designed, but
38 the BLFS editors find the <envar>PATH</envar> method easiest.</para>
40 <para> The advantage of installing in <filename
41 class='directory'>/usr</filename> is that no updates to the
42 <filename>/etc/</filename> or
43 <filename>/etc/man_db.conf</filename> files are required. The package files
44 are distributed within several subdirectories of the <filename
45 class='directory'>/usr</filename> hierarchy. This is the method that most
46 commercial distributions use. The disadvantage for BLFS users is that this
47 Qt instance cannot be upgraded while it is in use. For instance, it cannot
48 be upgraded from a running KDE environment. It also precludes having
49 multiple versions of Qt on your system and does not allow reverting to
50 an existing, known working instance of Qt.</para>
52 <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
58 this method, an update can be made without overwriting a previous
59 installation and users can easily revert to a previous version by changing
60 one symbolic link or merely changing the PATH variable. It also allows a
61 developer to maintain multiple versions of <application>Qt4</application>
62 or <application>Qt5</application> for testing. </para>
Note: See TracBrowser for help on using the repository browser.