diff -r 000000000000 -r 61163b28edca imakerplugin/com.nokia.s60tools.imaker.doc.user/html/tasks/taskPreferences.html --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/imakerplugin/com.nokia.s60tools.imaker.doc.user/html/tasks/taskPreferences.html Tue Jan 12 13:17:53 2010 -0600 @@ -0,0 +1,47 @@ + + + +
+ + +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.
+To save the fields of a configuration to a file, do the following:
To modify the values +of the variables of the selected product (or makefile), select the Settings + tab in the iMaker dialog. See the following example:
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.
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.
+
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.
+