core/com.nokia.carbide.cpp.doc.user/html/tasks/projects/prj_creating_sis_file.htm
changeset 1929 e42423cc31d4
parent 1920 b6a66d85e102
child 2009 b622387629d6
equal deleted inserted replaced
1928:cfa3a98b5df2 1929:e42423cc31d4
    19 </ul>
    19 </ul>
    20 <p>When a phone target build detects a PKG file at the end of a build, a post-link stage will be executed to create a SIS file, that is: </p>
    20 <p>When a phone target build detects a PKG file at the end of a build, a post-link stage will be executed to create a SIS file, that is: </p>
    21 <ul>
    21 <ul>
    22   <li>For non-Platform Security SDKs (pre-OS 9.x), <span class="code">makesis</span> is called</li>
    22   <li>For non-Platform Security SDKs (pre-OS 9.x), <span class="code">makesis</span> is called</li>
    23 </ul>
    23 </ul>
    24 <p>Depending upon which tool is used, you will  need to complete some entries in the<a href="../../reference/build_properties/pane_build_config_sis.htm"> SIS Builder</a> pane of the Carbide Build Configurations panel of the project Properties dialog box. You can access this pane by selecting a project in the Project Explorer view and select <b>Project &gt; Properties</b> &gt;  <b>Carbide Build Configurations</b>. Fill in the necessary information to add PKG files to the project for downloading. </p>
    24 <p>Depending upon which tool is used, you will  need to complete some entries in the <a href="../../reference/build_properties/pane_build_config_sis.htm">SIS Builder</a> pane of the Carbide Build Configurations panel of the project Properties dialog box. You can access this pane by selecting a project in the <a href="../../reference/view_proj_explorer.htm">Project Explorer</a> view and select <b>Project &gt; Properties</b> <strong>&gt; Carbide.c++ &gt; </strong><b>Carbide Build Configurations</b>. Fill in the necessary information to add PKG files to the project for downloading. </p>
    25 <table width="88%"  border="0" cellpadding="2" cellspacing="0">
    25 <table width="88%"  border="0" cellpadding="2" cellspacing="0">
    26   <tr>
    26   <tr>
    27     <th width="19%" scope="col">Tool</th>
    27     <th width="19%" scope="col">Tool</th>
    28     <th width="81%" scope="col">Explanation</th>
    28     <th width="81%" scope="col">Explanation</th>
    29   </tr>
    29   </tr>
    30   <tr>
    30   <tr>
    31     <td><b>SIS Builder </b></td>
    31     <td><b>SIS Builder </b></td>
    32     <td><p>Use the <b>Add</b> control to add one or more SIS or PKG files to the project up to the maximum number Carbide supports. Note that the <b>SIS Builder</b> pane operates on a build configuration level. You will need to add files in this pane for every build configuration in the project. </p>
    32     <td><p>Use the <b>Add</b> control to add one or more SIS or PKG files to the project up to the maximum number Carbide supports. Note that the <b>SIS Builder</b> pane operates on a build configuration level. You will need to add files in this pane for every build configuration in the project. </p>
    33       <p>In addition, any PKG file added here is picked up by the <a href="../../projects/launch/page_installation.htm">Installation</a> tab in Application TRK configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one. </p>
    33       <p>In addition, any PKG file added here is picked up by the <a href="../../projects/launch/page_installation.htm">Installation</a> tab in Application TRK configurations. However, as only one SIS file can be debugged at a time you must specify which SIS/PKG file to install for debugging purposes. This is handy if you have both a developer SIS file and a certified SIS file that you want to remain in sync during development. Both are always built but you only need to debug one. </p>
    34       <p><img src="images/sis_builder_tab.png" width="550" height="221" /></p>
    34       <p><img src="images/sis_builder_tab.png" width="573" height="203" /></p>
    35     <p class="figure">Figure 1 - SIS Builder tab </p></td>
    35     <p class="figure">Figure 1 - SIS Builder tab </p></td>
    36   </tr>
    36   </tr>
    37   <tr>
    37   <tr>
    38     <td><b>SIS Properties </b></td>
    38     <td><b>SIS Properties </b></td>
    39     <td><div align="center">
    39     <td><div align="center">
    40       <p align="left">Complete the PKG File, and Signing Options settings in the <a href="../../reference/build_properties/wnd_sis_properties.htm">SIS Properties</a> dialog. By default, SIS files are output in the directory of the original SIS file.</p>
    40       <p align="left">Complete the PKG File, and Signing Options settings in the <a href="../../reference/build_properties/wnd_sis_properties.htm">SIS Properties</a> dialog. By default, SIS files are output in the directory of the original SIS file.</p>
    41       <p><img src="../../reference/images/wnd_sis_properties.png" width="455" height="452"></p>
    41       <p><img src="../../reference/images/wnd_sis_properties.png" width="533" height="463"></p>
    42       <p class="figure">Figure 2 - SIS Properties dialog </p>
    42       <p class="figure">Figure 2 - SIS Properties dialog </p>
    43       </div></td>
    43       </div></td>
    44   </tr>
    44   </tr>
    45 </table>
    45 </table>
    46 <p>For phones that utilize OS 9.x, all SIS files must be signed before being installed on a device. You can specify your certificate and key pair file in the SIS Builder pane. By default, if no certificate/key pair is defined, temporary ones will be created in the build directory. This is a process called self-signing. However, not all devices allow self-signed applications to be installed. For information on obtaining certificate and key pairs for your development please visit <a href="https://www.symbiansigned.com">https://www.symbiansigned.com</a>.</p>
    46 <p>For phones that utilize OS 9.x, all SIS files must be signed before being installed on a device. You can specify your certificate and key pair file in the SIS Builder pane. By default, if no certificate/key pair is defined, temporary ones will be created in the build directory. This is a process called self-signing. However, not all devices allow self-signed applications to be installed. For information on obtaining certificate and key pairs for your development please visit <a href="https://www.symbiansigned.com">https://www.symbiansigned.com</a>.</p>