equal
deleted
inserted
replaced
|
1 .. ============================================================================ |
|
2 Name : running.rst |
|
3 Part of : Helium |
|
4 |
|
5 Copyright (c) 2009 Nokia Corporation and/or its subsidiary(-ies). |
|
6 All rights reserved. |
|
7 This component and the accompanying materials are made available |
|
8 under the terms of the License "Eclipse Public License v1.0" |
|
9 which accompanies this distribution, and is available |
|
10 at the URL "http://www.eclipse.org/legal/epl-v10.html". |
|
11 |
|
12 Initial Contributors: |
|
13 Nokia Corporation - initial contribution. |
|
14 |
|
15 Contributors: |
|
16 |
|
17 Description: |
|
18 |
|
19 ============================================================================ |
|
20 |
1 .. index:: |
21 .. index:: |
2 module: Running Helium |
22 module: Running Helium |
3 |
23 |
4 ############## |
24 ############## |
5 Running Helium |
25 Running Helium |
98 |
118 |
99 When a build is running the targets being executed are listed on the screen there is no need to pipe this to a file as the ant targets are logged in the ``\*_main.ant.log`` for product and IDO builds. Once the build is complete it will say on the screen whether the build was successful or failed. If it has failed it should give an indication of where and why it failed on the screen but for more information you must examine the output logs. If the build says it was successfult this does not necessarily mean that the build compiled all components successfully, you must examine the logs to check that all is compiled and linked correctly. See :ref:`Troubleshooting-label` for information on logs and where they kept. |
119 When a build is running the targets being executed are listed on the screen there is no need to pipe this to a file as the ant targets are logged in the ``\*_main.ant.log`` for product and IDO builds. Once the build is complete it will say on the screen whether the build was successful or failed. If it has failed it should give an indication of where and why it failed on the screen but for more information you must examine the output logs. If the build says it was successfult this does not necessarily mean that the build compiled all components successfully, you must examine the logs to check that all is compiled and linked correctly. See :ref:`Troubleshooting-label` for information on logs and where they kept. |
100 |
120 |
101 The result of the build (compiled files, linked (flash) files etc.) are stored in the usual folders and directories under the ``\epoc32`` directory. |
121 The result of the build (compiled files, linked (flash) files etc.) are stored in the usual folders and directories under the ``\epoc32`` directory. |
102 |
122 |
|
123 .. index:: |
|
124 single: Running build operations |
|
125 |
|
126 Running build operations |
|
127 ======================== |
|
128 |
|
129 Setting the build number |
|
130 ------------------------- |
|
131 |
|
132 The :hlm-p:`build.number` property is typically not defined in a configuration file, as it changes for every new build. It should be defined as a command line parameter:: |
|
133 |
|
134 -Dbuild.number=123 |
|
135 |
|
136 A shortcut can also be used:: |
|
137 |
|
138 -Dbn=123 |
|
139 |
|
140 .. index:: |
|
141 single: Setting the team property |
|
142 |
|
143 .. _Setting-Team_properties-label: |
|
144 |
|
145 Setting the team property |
|
146 -------------------------- |
|
147 |
|
148 ``SET TEAM=<team-name>`` (this defines which team-specific XML file from ``../site/${r'$'}{env.TEAM}.ant.xml`` is used for build configuration). |
|
149 |
103 |
150 |
104 .. index:: |
151 .. index:: |
105 single: Logging |
152 single: Logging |
106 |
153 |
107 Logging |
154 Logging |