/doc/src/platforms/emb-install.qdoc

https://bitbucket.org/ultra_iter/qt-vtl · Unknown · 188 lines · 139 code · 49 blank · 0 comment · 0 complexity · ee9d366f00903ecc224b71d19efbfbb1 MD5 · raw file

  1. /****************************************************************************
  2. **
  3. ** Copyright (C) 2012 Nokia Corporation and/or its subsidiary(-ies).
  4. ** All rights reserved.
  5. ** Contact: Nokia Corporation (qt-info@nokia.com)
  6. **
  7. ** This file is part of the documentation of the Qt Toolkit.
  8. **
  9. ** $QT_BEGIN_LICENSE:FDL$
  10. ** GNU Free Documentation License
  11. ** Alternatively, this file may be used under the terms of the GNU Free
  12. ** Documentation License version 1.3 as published by the Free Software
  13. ** Foundation and appearing in the file included in the packaging of
  14. ** this file.
  15. **
  16. ** Other Usage
  17. ** Alternatively, this file may be used in accordance with the terms
  18. ** and conditions contained in a signed written agreement between you
  19. ** and Nokia.
  20. **
  21. **
  22. **
  23. **
  24. ** $QT_END_LICENSE$
  25. **
  26. ****************************************************************************/
  27. /*!
  28. \page qt-embedded-install.html
  29. \title Installing Qt for Embedded Linux
  30. \ingroup qt-embedded-linux
  31. \ingroup installation
  32. \brief How to install Qt for Embedded Linux.
  33. This document describes how to install \l{Qt for Embedded Linux} in your
  34. development environment:
  35. \tableofcontents
  36. Please see the \l{Cross-Compiling Qt for Embedded Linux Applications}{cross
  37. compiling} and \l{Deploying Qt for Embedded Linux Applications}{deployment}
  38. documentation for details on how to install \l{Qt for Embedded Linux} on
  39. your target device.
  40. Note also that this installation procedure is written for Linux,
  41. and that it may need to be modified for other platforms.
  42. \section1 Step 1: Installing the License File (commercial editions only)
  43. If you have the commercial edition of \l{Qt for Embedded Linux}, the first step
  44. is to install your license file as \c $HOME/.qt-license.
  45. For the open source version you do not need a license file.
  46. \section1 Step 2: Unpacking the Archive
  47. First uncompress the archive in the preferred location, then
  48. unpack it:
  49. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 0
  50. This document assumes that the archive is unpacked in the
  51. following directory:
  52. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 1
  53. \section1 Step 3: Building the Library
  54. Before building the \l{Qt for Embedded Linux} library, run the \c
  55. ./configure script to configure the library for your development
  56. architecture. You can list all of the configuration system's
  57. options by typing
  58. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc embedded help
  59. The \l{Configuration Options for Qt} page gives a brief overview
  60. of these.
  61. Note that by default, \l{Qt for Embedded Linux} is configured for
  62. installation in the \c{/usr/local/Trolltech/QtEmbedded-%VERSION%}
  63. directory, but this can be changed by using the \c{-prefix}
  64. option. Alternatively, the \c{-prefix-install} option can be used
  65. to specify a "local" installation within the source directory.
  66. The configuration system is also designed to allow you to specify
  67. your platform architecture:
  68. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 2
  69. In general, all Linux systems which have framebuffer support can
  70. use the \c generic architecture. Other typical architectures are
  71. \c x86, \c arm and \c mips.
  72. \note If you want to build Qt for Embedded Linux for use with a virtual
  73. framebuffer, pass the \c{-qvfb} option to the \c configure
  74. script.
  75. To create the library and compile all the demos, examples, tools,
  76. and tutorials, type:
  77. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 3
  78. On some systems the \c make utility is named differently, e.g. \c
  79. gmake. The \c configure script tells you which \c make utility to
  80. use.
  81. If you did not configure \l{Qt for Embedded Linux} using the \c{-prefix-install}
  82. option, you need to install the library, demos, examples, tools,
  83. and tutorials in the appropriate place. To do this, type:
  84. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 4
  85. and enter the root password.
  86. \note You can use the \c INSTALL_ROOT environment variable to specify
  87. the location of the installed files when invoking \c{make install}.
  88. \section1 Step 4: Adjusting the Environment Variables
  89. In order to use \l{Qt for Embedded Linux}, the \c PATH variable must be extended
  90. to locate \c qmake, \c moc and other \l{Qt for Embedded Linux} tools, and the \c
  91. LD_LIBRARY_PATH must be extended for compilers that do not support
  92. \c rpath.
  93. To set the \c PATH variable, add the following lines to your \c
  94. .profile file if your shell is bash, ksh, zsh or sh:
  95. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 5
  96. In case your shell is csh or tcsh, add the following line to the
  97. \c .login file instead:
  98. \snippet doc/src/snippets/code/doc_src_emb-install.qdoc 6
  99. If you use a different shell, please modify your environment
  100. variables accordingly.
  101. For compilers that do not support \c rpath you must also extend
  102. the \c LD_LIBRARY_PATH environment variable to include
  103. \c /usr/local/Trolltech/QtEmbedded-%VERSION%/lib. Note that on Linux
  104. with GCC, this step is not needed.
  105. \section1 Step 5: Building the Virtual Framebuffer
  106. For development and debugging, \l{Qt for Embedded Linux} provides a virtual
  107. framebuffer as well as the option of running \l{Qt for Embedded Linux} as a VNC
  108. server. For a description of how to install the virtual
  109. framebuffer and how to use the VNC protocol, please consult the
  110. documentation at:
  111. \list
  112. \o \l {The Virtual Framebuffer}
  113. \o \l {The VNC Protocol and Qt for Embedded Linux}
  114. \endlist
  115. Note that the virtual framebuffer requires a Qt for X11
  116. installation. See \l {Installing Qt for X11 Platforms} for details.
  117. The Linux framebuffer, on the other hand, is enabled by default on
  118. all modern Linux distributions. For information on older versions,
  119. see \l http://en.tldp.org/HOWTO/Framebuffer-HOWTO.html. To test
  120. that the Linux framebuffer is set up correctly, use the program
  121. provided by the \l {Testing the Linux Framebuffer} document.
  122. That's all. \l{Qt for Embedded Linux} is now installed.
  123. \table 100%
  124. \row
  125. \o
  126. \bold {Customizing the Qt for Embedded Linux Library}
  127. When building embedded applications on low-powered devices,
  128. reducing the memory and CPU requirements is important.
  129. A number of options tuning the library's performance are
  130. available. But the most direct way of saving resources is to
  131. fine-tune the set of Qt features that is compiled. It is also
  132. possible to make use of accelerated graphics hardware.
  133. \list
  134. \o \l {Fine-Tuning Features in Qt}
  135. \o \l {Qt Performance Tuning}
  136. \o \l {Adding an Accelerated Graphics Driver to Qt for Embedded Linux}
  137. \endlist
  138. \endtable
  139. */