This chapter does not contain libraries that are required to run X. It does contain libraries that enhance X. In some cases the enhancement is as simple as font support. In others it is as complex as libraries that sit between X and applications that run on X whose purpose is to standardize the look and feel and inter-process communications for different applications. They also assist programmers by supplying common elements.
The Qt package contains a C++ GUI library. This is useful for creating graphical applications or executing graphical applications that are dynamically linked to the Qt library. One of the major users of Qt is KDE.
Download (FTP): ftp://ftp.trolltech.com/qt/source/qt-x11-free-3.3.4.tar.bz2
Download MD5 sum: 027f4e82fbe592b39d2f160bfb3a73af
Download size: 13.8 MB
Estimated disk space required: 250 MB
Estimated build time: 15.5 SBU (full), 10.9 SBU (sub-tools)
There are several ways to install a complicated package such as Qt. The files are not completely position independent. Installation procedures execute the program pkg-config to determine the location of package executables, libraries, headers, and other files. For Qt, pkg-config will look for the file lib/pkgconfig/qt-mt.pc which must be modified if relocating the package. This file is set up correctly by the build process.
The default installation places the files in /usr/local/qt/. Many commercial distributions place the files in the system's /usr hierarchy. The package can also be installed in an arbitrary directory.
This section will demonstrate two different methods.
The build time for Qt is quite long. If you want to save some time and don't want the tutorials and examples, change the first make line to:
The advantage of this method is that no updates to the /etc/ld.so.conf or /etc/man.conf files are required. The package files are distributed within several subdirectories of the /usr hierarchy. This is the method that most commercial distributions use.
If Qt is being reinstalled, run the following commands from a console or non-Qt based window manager. It overwrites Qt libraries that should not be in use during the install process.
sed -i -e 's:$(QTDIR)/include:&/qt:' \ -e 's:$(QTDIR)/lib:&/qt:' \ mkspecs/linux*/qmake.conf && bash export PATH=$PWD/bin:$PATH && export LD_LIBRARY_PATH=$PWD/lib:$LD_LIBRARY_PATH && ./configure -prefix /usr -docdir /usr/share/doc/qt \ -headerdir /usr/include/qt -plugindir /usr/lib/qt/plugins \ -datadir /usr/share/qt -translationdir /usr/share/qt/translations \ -sysconfdir /etc/qt -qt-gif -system-zlib -system-libmng \ -no-exceptions -thread -plugin-imgfmt-png \ -system-libjpeg -system-libpng && find -type f -name Makefile | xargs sed -i "s@-Wl,-rpath,/usr/lib@@g" && make && exit
Now, as the root user:
make install && ln -v -sf libqt-mt.so /usr/lib/libqt.so && cp -v -r doc/man /usr/share && cp -v -r examples /usr/share/doc/qt
This is the method recommended by the Qt developers. It has the advantage of keeping all the package files consolidated in a dedicated directory hierarchy. By using this method, an update can be made without overwriting a previous installation and users can easily revert to a previous version by changing one symbolic link.
The Qt developers use a default location of /usr/local/qt/, however this procedure puts the files in /opt/qt-3.3.4/ and then creates a symbolic link to /opt/qt/.
bash export QTDIR=$PWD && export LD_LIBRARY_PATH=$PWD/lib:$LD_LIBRARY_PATH && export PATH=$PWD/bin:$PATH && ./configure -prefix /opt/qt-3.3.4 -qt-gif -system-libpng \ -system-libmng -system-zlib -system-libjpeg -no-exceptions \ -thread -plugin-imgfmt-png && make && exit
Now, as the root user:
make install && ln -v -sfn qt-3.3.4 /opt/qt && ln -v -s libqt-mt.so /opt/qt/lib/libqt.so && cp -v -r doc/man /opt/qt/doc && cp -v -r examples /opt/qt/doc
If you pass the -plugin-sql-[driver] switch to the configure command, you must also pass -I[/path/to/sql/headers] so make can find the appropriate header files.
sed -i -e ... mkspecs/linux*/qmake.conf: Directories in qmake.conf need to be adjusted to match the BLFS Method 1 installation directories.
bash: This command enters a sub-shell to isolate environment changes.
export QTDIR=$PWD: This command defines where the root of the Qt directory is located.
export LD_LIBRARY_PATH=$PWD/lib:$LD_LIBRARY_PATH: This command allows the not yet installed Qt libraries to be used by the not yet installed Qt programs.
export PATH=$PWD/bin:$PATH: This command allows the build process to find supporting executables.
-qt-gif: This switch adds support for gif files to the libraries.
-system-zlib -system-libpng: This switch forces the build instructions to use the shared libraries that are on your system instead of creating a custom set of support libraries for these functions.
-plugin-imgfmt-png: This switch enables libpng to be linked to at runtime.
-no-exceptions: This switch disables the exceptions coding generated by the C++ compiler.
-thread: This switch adds support for multi-threading.
find -type f -name Makefile | xargs sed -i "s@-Wl,-rpath,/usr/lib@@g": This command removes hardcoded run-time paths. Otherwise, uic always tries to run with Qt libraries in /usr/lib.
ln -v -s libqt-mt.so /usr/lib/libqt.so: This command allows configure scripts to find a working Qt installation.
cp -v -r doc/man /usr/share (or /opt/qt/doc): This command installs the man pages which are missed by make install.
cp -v -r examples /usr/share/doc/qt (or /opt/qt/doc): This command installs the examples which are missed by make install.
exit: This command returns to the parent shell and eliminates environment variables set earlier.
The QTDIR environment variable needs to be set when building packages that depend on Qt. Add the following to the .bash_profile initialization script for each user that builds packages using the Qt libraries. Alternatively, the variable can be set in the system wide /etc/profile file.
For Method 1 (This is optional, only set this if an application is unable to find the installed libraries):
or for Method 2:
If you installed Qt using Method 2, you also need to update the following configuration files so that Qt is correctly found by other packages and system processes.
Update the /etc/ld.so.conf and /etc/man.conf files:
cat >> /etc/ld.so.conf << "EOF" && # Begin qt addition to /etc/ld.so.conf /opt/qt/lib # End qt addition EOF ldconfig && cat >> /etc/man.conf << "EOF" # Begin qt addition to man.conf MANPATH /opt/qt/doc/man # End qt addition to man.conf EOF
Update the PKG_CONFIG_PATH environment variable in your ~/.bash_profile or /etc/profile with the following:
If you want the Qt executables in your shell search path, update the PATH environment variable in your ~/.bash_profile or /etc/profile to include /opt/qt/bin.
As with most libraries, there is no explicit configuration to do. After updating /etc/ld.so.conf as explained above, run /sbin/ldconfig so that ldd can find the shared libraries.
is a tool for presenting on-line documentation.
is a full-fledged GUI builder. It includes powerful features such as preview mode, automatic widget layout, support for custom widgets, and an advanced property editor.
provides support for translating applications into local languages.
is a simple command line tool. It reads a Qt project file and produces message files used by the application.
reads a Qt project file, finds the translatable strings in the specified source, header and Qt Designer interface files, and produces or updates the translation files listed in the project file.
generates Qt meta object support code.
is a tool for converting Qt message file formats.
qmake uses information stored in project files to determine what should go in the makefiles it generates.
is used to customize the appearance of Qt applications.
is a Qt user interface compiler.
Last updated on 2005-08-14 15:03:38 -0600