1 <?xml version="1.0" encoding="utf-8"?>

     2 <!-- Copyright (c) 2007-2010 Nokia Corporation and/or its subsidiary(-ies) All rights reserved. -->

     3 <!-- This component and the accompanying materials are made available under the terms of the License 

     4 "Eclipse Public License v1.0" which accompanies this distribution, 

     5 and is available at the URL "http://www.eclipse.org/legal/epl-v10.html". -->

     6 <!-- Initial Contributors:

     7     Nokia Corporation - initial contribution.

     8 Contributors: 

     9 -->

    10 <!DOCTYPE concept

    11   PUBLIC "-//OASIS//DTD DITA Concept//EN" "concept.dtd">

    12 <concept id="GUID-50F216D0-242A-5796-BDCC-7AAB28535458" xml:lang="en"><title>Features

    13 command syntax</title><prolog><metadata><keywords/></metadata></prolog><conbody>

    14 <section><title>Purpose</title><p>The <codeph>features</codeph> tool processes

    15 the Feature Database Manager (xml file) and generates the header file, feature

    16 choices obey file and/or <filepath>features.dat</filepath> file. The header

    17 file contains feature UIDs. The feature choices obey file is used to create

    18 different ROM images. The <filepath>features.dat</filepath> file which is

    19 a binary file, is used as a default configuration file by the Symbian emulator.

    20 The <codeph>features</codeph> tool accepts both feature manager and feature

    21 registry database as input, and for the feature registry database, it generates

    22 only <filepath>features.dat</filepath>. </p> </section>

    23 <section><title>Syntax</title><codeblock xml:space="preserve">features [options] &lt;xml database  file&gt; [&lt;xml database file1&gt; &lt;xml database file2&gt;...]</codeblock><p>The following options can be used: </p><table id="GUID-4A4B3EE7-8900-404E-8404-955DB9031706">

    24 <tgroup cols="2"><colspec colname="col1"/><colspec colname="col2"/>

    25 <tbody>

    26 <row>

    27 <entry><b>Options</b></entry>

    28 <entry><b>Description</b></entry>

    29 </row>

    30 <row>

    31 <entry><codeph>-r[=&lt;destination path&gt;]</codeph> or <codeph>--hdrfile[=&lt;destination

    32 path&gt;]</codeph></entry>

    33 <entry>Creates a header file in <codeph>&lt;destination path&gt;</codeph> or

    34 in the default path <filepath>\epoc32\include</filepath>, if the destination

    35 path is not specified. </entry>

    36 </row>

    37 <row>

    38 <entry><codeph>-i[=&lt;destination path&gt;]</codeph> or <codeph>--ibyfile[=&lt;destination

    39 path&gt; </codeph></entry>

    40 <entry>Creates an IBY file in <codeph>&lt;destination path&gt;</codeph> or in

    41 the default path <filepath>\epoc32\rom\include\</filepath>, if the destination

    42 path is not specified. </entry>

    43 </row>

    44 <row>

    45 <entry><codeph>-d[=&lt;destination path&gt;]</codeph> or <codeph>--datfile[=&lt;destination

    46 path&gt;]</codeph></entry>

    47 <entry>Creates <filepath>features.dat</filepath> file in <codeph>&lt;destination

    48 path&gt;</codeph> or in the current directory, if the destination path is not

    49 specified. </entry>

    50 </row>

    51 <row>

    52 <entry><codeph>-c[=&lt;destination path&gt;]</codeph> or <codeph>--convert[=&lt;destination

    53 path&gt;]</codeph></entry>

    54 <entry>Converts the given feature registry database into a feature manager

    55 database (for example, <filepath>featureregistryname_converted.xml</filepath>)

    56 in <codeph>&lt;destination path&gt;</codeph> or in the current directory, if

    57 the destination path is not specified. <note>The converted file is named as <filepath>featureregistryname_converted.xml</filepath> by

    58 default. See <b>Conversion of feature registry DB to feature manager DB</b>.</note> </entry>

    59 </row>

    60 <row>

    61 <entry><codeph>-s</codeph> or <codeph>--strict</codeph></entry>

    62 <entry>Enables strict mode.</entry>

    63 </row>

    64 <row>

    65 <entry><codeph>-v</codeph> or<codeph> --verbose</codeph> </entry>

    66 <entry>Enables verbose mode.</entry>

    67 </row>

    68 <row>

    69 <entry><codeph>-h</codeph> or <codeph>--help</codeph> </entry>

    70 <entry>Displays help.</entry>

    71 </row>

    72 <row>

    73 <entry><codeph>--version</codeph> </entry>

    74 <entry>Displays the version of the tool.</entry>

    75 </row>

    76 </tbody>

    77 </tgroup>

    78 </table><p>The features tool also allows you to specify a combination of options

    79 (for example, <codeph>features -rcv</codeph>).   </p><p><codeph>&lt;xml database

    80 file&gt;</codeph> can be either a Feature Registry database (<filepath>featureUIDs.xml</filepath>)

    81 or a Feature Manager database (<filepath>featuredatabase.xml</filepath>) </p></section>

    82 </conbody></concept>