Changeset 145 in tspsg-svn for trunk/docs/dox/install.dox


Ignore:
Timestamp:
Oct 15, 2010, 8:15:43 AM (14 years ago)
Author:
laleppa
Message:
  • Updated INSTALLs and ChangeLogs? with the latest information.
  • Regenerated tspsg.tag.

NB: This will be the first public beta release.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/docs/dox/install.dox

    r134 r145  
    1919     -# \ref i_s42
    2020     -# \ref i_s43
    21         -# \ref i_s431
    22         -# \ref i_s432
    2321     -# \ref i_s44
     22        -# \ref i_s441
     23        -# \ref i_s442
    2424     -# \ref i_s45
    2525     -# \ref i_s46
     26     -# \ref i_s47
    2627  -# \ref i_s5
    2728  -# \ref i_s6
     
    5051Also, the following assumptions are made:
    5152
    52   - For \b Linux/UNIX: \c lrelease and \c qmake are avilable in \c $PATH.
     53  - For \b Linux/UNIX/BSD: \c lrelease and \c qmake are avilable in \c $PATH.
    5354  - For \b Windows (\em minGW) and \b Symbian: you have installed <em>Qt SDK</em> or
    5455    prebuilt libraries and have Start Menu items for Qt tools.
     
    7475\subsection i_s41 GENERAL INSTALLATION PROCEDURE
    7576
     77To be able ot build \b TSPSG you need to have the following Qt modules:
     78\em QtCore, \em QtGui and \em QtSvg. The first two are required, the last one is
     79optional. To get support for additional image formats (i.e., \b JPEG and
     80\b TIFF) you'll additionally need corresponding <em>Qt imageformats</em> plugins.
     81
     82If you want to build \b TSPSG without \b SVG support add \c nosvg to \c qmake
     83\c CONFIG parameter, so that qmake command will typically be:
     84
     85\verbatim
     86qmake CONFIG+=release CONFIG+=nosvg
     87\endverbatim
     88
     89This way you will not depend on \em QtSvg module but will not be able to
     90export solution graph in \b SVG format.
     91
     92
     93\b TSPSG uses \c qmake \c PREFIX parameter to determine installation path for
     94make install command. If you don't specify it when running \c qmake, it
     95will be assigned the default value depending on the platform:
     96
     97<table>
     98<tr><th>Platform</th><th>Default \c PREFIX value</th></tr>
     99<tr><td>\b Linux/UNIX/BSD</td><td>\c /usr</td></tr>
     100<tr><td>\b Windows</td><td></td>\c \%PROGRAMFILES\% environment variable (usually, it is <tt>C:\\Program Files</tt>)</tr>
     101<tr><td><b>Windows CE/Mobile</b></td><td><tt>\\Program Files</tt></td></tr>
     102<tr><td>\b Symbian</td><td></td><em>\<ignored></em></tr>
     103</table>
     104
     105\note Please, note that there are no installation and/or packaging
     106rules for \b MacOS and other platforms not mentioned in this table.
     107
     108
     109By default, \b TSPSG uses precompiled header when being built. If you
     110experience problems with it you may add \c CONFIG+=nopch parameter to
     111\c qmake to disable the generation and use of the precompiled header.
     112
     113<hr>
     114
     115\subsection i_s42 GENERAL INSTALLATION PROCEDURE
     116
    76117On most platforms the general building and installation procedure is:
    77118
     
    87128<hr>
    88129
    89 \subsection i_s42 LINUX/UNIX
     130\subsection i_s43 LINUX/UNIX/BSD
    90131
    91132Open a shell, navigate to the directory where you have \b TSPSG source
     
    126167depending on your distribution.
    127168
    128 By default, executable will go to \c /usr/bin, \c COPYING.txt and \c README.txt will go
    129 to \c /usr/share/TSPSG, translations will go \c /usr/share/TSPSG/l10n, all docs
    130 will go to <tt>/usr/share/doc/TSPSG-\<VERSION></tt>.
    131 
    132 <hr>
    133 
    134 \subsection i_s43 WINDOWS
     169The executable goes to \c \<PREFIX>/bin; \c COPYING, \c ChangeLog.txt, \c README.txt
     170and \c INSTALL.txt go to \c \<PREFIX>/share/doc/TSPSG-\<VERSION>.
     171
     172<hr>
     173
     174\subsection i_s44 WINDOWS
     175
     176\b TSPSG will be installed to \c \<PREFIX>\\TSPSG folder.
    135177
    136178\note Please, read the section \ref i_s7 after reading this section.
    137179
    138 \subsubsection i_s431 USING MINGW
     180\subsubsection i_s441 USING MINGW
    139181
    140182Unpack the downloaded source code of \b TSPSG with your favourite
     
    157199\endverbatim
    158200
    159 \b TSPSG will be installed to \c \%PROGRAMFILES\%\\TSPSG folder (usually, it is
    160 <tt>C:\\Program Files\\TSPSG</tt>).
    161 
    162 
    163 \subsubsection i_s432 USING VISUAL STUDIO
     201
     202\subsubsection i_s442 USING VISUAL STUDIO
    164203
    165204Unpack the downloaded source code of \b TSPSG with your favourite
     
    180219\endverbatim
    181220
    182 \b TSPSG will be installed to \c \%PROGRAMFILES\%\\TSPSG folder (usually, it is
    183 <tt>C:\\Program Files\\TSPSG</tt>).
    184 
    185 <hr>
    186 
    187 \subsection i_s44 WINDOWS CE/MOBILE
     221<hr>
     222
     223\subsection i_s45 WINDOWS CE/MOBILE
    188224
    189225Unpack the downloaded source code of \b TSPSG with your favourite
     
    215251<hr>
    216252
    217 \section i_s45 SYMBIAN
     253\section i_s46 SYMBIAN
    218254
    219255Unpack the downloaded source code of \b TSPSG with your favourite
     
    262298<hr>
    263299
    264 \subsection i_s46 OTHER PLATFORMS, SUPPORTED BY QT
     300\subsection i_s47 OTHER PLATFORMS, SUPPORTED BY QT
    265301
    266302While \b TSPSG is oficially supported only on \b Linux, \b Windows and <b>Windows
Note: See TracChangeset for help on using the changeset viewer.