imakerplugin/com.nokia.s60tools.imaker.doc.user/html/tasks/taskPreferences.html
author dpodwall
Tue, 12 Jan 2010 13:17:53 -0600
changeset 0 61163b28edca
child 11 217e69fc5beb
permissions -rw-r--r--
initial EPL conversion

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<?Pub Inc>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=iso-8859-1" />
<meta http-equiv="content-style-type" content="text/css" />
<title>Managing preferences</title>
<link href="../book.css" type="text/css" rel="stylesheet" />
</head>
<body>
<h2>Managing preferences</h2>  
<p>Before you can build a ROM image, you must define the preferences for a configuration. In iMaker,
a configuration can be thought of as a container of product and other information.</p> 
<ol>
<li>Select the project that you want to use as the basis for image creation. </li>
<li>Select <b>Open iMaker Dialog...</b> option from the iMaker pulldown menu on the toolbar. iMaker Extension will now start scanning the environtment to query 
information from the underlying iMaker commandline tool. This may take a while, but this action occurs only once for each project.</li>
<li>When the <b>iMaker Dialog</b> is opened, it is populated with data from the active environment. Default product is selected if one is configured, otherwise the first product is selected. 
User can change the product using the <b>Change...</b> button. Example is shown bellow. <p><img
src="images/iMakerPluginPreferences.png"></p></li>
<li>Once data is filled in the fields, a flashable image can be created. Press
the <b>Run</b> button at the bottom of the dialog. Remember to add the desired targets to the <b>selected</b> list of targets.</li>
</ol> 
<h3>Saving the preferences for a configuration</h3> 
<p>To save the fields of a configuration to a file, do the following: </p><ol>
<li>Press the <b>Save as...</b></li>
<li>Choose the parent folder where to save the file, it is recommended to save under the selected project. See below image.<p><img src="images/iMakerPluginSaveAction.png"></p></li>
<li>All saved preferences are visible in the <b>configuration</b> combobox on the top of the dialog. Any of these saved files can be activated and used for image creation.</li>

<a name="management"></a><h3>Settings tab</h3> <p>To modify the values
of the variables of the selected product (or makefile), select the <b>Settings
</b> tab in the iMaker dialog. See the following example: </p><p><img src="images/iMakerPluginPreferencesDetails.png"> Through this tab user can override the default variable values in the iMaker core. Any modified parameter will be passed to iMaker cmd throuht execution command.</p> 

<a name="debug"></a><h3>Debug tab</h3>
<p>The debug tab allows user to add binary and data files to the image. These files can be added to different sections of the image. The binary files can be easy changed to debug versions. Currently CORE and ROFS sections are supported. 
Files cannot be added to UDA for example through this tab.<br>
<img src="images/debug_tab.png"></p>

<a name="platsim"></a><h3>Platsim tab</h3>
<p>The contents of the platsim tab will be enabled, when you select a valid platsim configuration from the main tab. The platsim configuration must define USE_PLATSIM variable, in order it to be 
consider as valid. This variable must be non-empty. Users can edit the platsim configuration makefile and add USE_PLATSIM=1 then restart carbide.c++. Currently only all target is supported. All 
target creates an image, which contains all image sections (core, rofsx, ...) and configures the selected platsim instance with the created image. Selecting (run platsim after image creation) checkbox causes 
platsim instance to be started in the end of the image creation process.<br>
<img src="images/platsim_tab.png"> </p> 
<div id="footer">Copyright &copy; 2009 Nokia Corporation and/or its subsidiary(-ies). All rights reserved. 	License: <a href="http://www.eclipse.org/legal/epl-v10.html">http://www.eclipse.org/legal/epl-v10.html</a>.</div>
</body>
</html>