summaryrefslogtreecommitdiffstats
path: root/doc/src/s60-introduction.qdoc
blob: e6e6b7e1a529bf2aa53aa54c1f273c3d1afff5e0 (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
/****************************************************************************
**
** Copyright (C) 2008 Nokia Corporation and/or its subsidiary(-ies).
** Contact: Qt Software Information (qt-info@nokia.com)
**
** This file is part of the $MODULE$ of the Qt Toolkit.
**
** $TROLLTECH_DUAL_LICENSE$
**
****************************************************************************/

/*!
    \page s60-with-qt-introduction.html

    \title S60 - Introduction to using Qt
    \brief An introduction to Qt for S60 developers.
    \ingroup howto
    \ingroup qts60

    \tableofcontents

    \section1 Installing Qt

    Follow the instructions found in \l{Installing Qt on S60}.

    \section1 Building your own applications

    If you are new to Qt development, have a look at \l{How to Learn Qt}. 
    In general, the difference between developing a
    Qt application on S60 compared to any of the other platforms supported
    by Qt is not that big.

    Once you have crated a \c .pro file for your project, generate the
    Carbide specific \c Bld.inf and \c .mmp files this way:

    \snippet doc/src/snippets/code/doc_src_s60-introduction.qdoc 0

    For more information on how to use qmake have a look at the \l
    {qmake Tutorial}.

    Now you can build the Qt on S60 application with standard build
    tools. By default, running \c make will produce binaries for the
    emulator. However, S60 comes with several alternative build targets,
    as shown in the table below:

    \table
    \row \o \c debug-winscw  \o Build debug binaries for the emulator (default).
                                It is currently not possible to build release
                                binaries for the emulator.
    \row \o \c debug-gcce    \o Build debug binaries for hardware using GCCE.
    \row \o \c release-gcce  \o Build release binaries for hardware using GCCE.
    \row \o \c debug-armv5   \o Build debug binaries for hardware using RVCT.
    \row \o \c release-armv5 \o Build release binaries for hardware using RVCT.
    \row \o \c run           \o Run the emulator binaries from the build directory.
    \endtable

    The following lines perform a debug build for the emulator
    and deploy all the needed files:

    \snippet doc/src/snippets/code/doc_src_s60-introduction.qdoc 1

    To work on your project in Carbide, simply import the \c .pro file
    by right clicking on the project explorer and executing "Import...".

    \section1 Installing your own applications

    To install your own applications on hardware, Qt comes with a tool called
    \c createpackage. When used on the \c .pkg files created by qmake, it
    will produce a \c .sisx file that can be installed to the device. For
    example:

    \snippet doc/src/snippets/code/doc_src_s60-introduction.qdoc 2

    If you want to install the program immediately, make sure that the device
    is connected to the computer in "PC Suite" mode, and run \c createpackage
    with the \c -i switch, like this:

    \snippet doc/src/snippets/code/doc_src_s60-introduction.qdoc 3
*/