57      <blockquote>

    58          <p><img src="../reference/images/import_bld_inf_01.png" alt="Select Symbian bld.inf file to import" width="525" height="550"></p>

    59      </blockquote>

    60      <ol start="3">

    61 		 <li> 

    62 			 Type the location of the bld.inf file to import, or browse to the file using the Browse button. </li>

    63 		  <p class="Image"><img src="../reference/images/import_bld_inf_02.png" alt="Select bld.inf file to import" width="573" height="550"></p>

    64 		  <p class="note"><strong>NOTE</strong> Depending upon which SDKs are installed, you may see both SBSv1 and SBSv2 builders available. It is recommended that SBSv2 be the primary choice as SBSv1 has been deprecated for future Symbian OS development.</p>

    65 		  <p class="Image">SBSv2   works with recent versions of Symbian^3 and Symbian ^4 SDKs. Both  SBSv1 and SBSv2 are GNU make based build systems.&nbsp; SBSv1 uses Perl to generate make files,  while SBSv2 uses Python. Select the appropriate builder for your project.</p>

    66 		  When building for  SBSv2, the builder will set <span class="code">EPOCROOT</span> to the absolute path (including drive  letter) to the kit for the active build configuration.&nbsp; It will also add the path to the sbs bin  directory to the start of the <span class="code">PATH</span> variable.&nbsp;  This is derived from the SBS_HOME environment variable.

    67 		  <p class="Image">For SBSv2, all  build configurations (platform/target), including the built-in platforms  (WINSCW, ARMV5), are declared in xml files in the <span class="code">\sbs\lib\config</span> directory.  The Build  Configurations selection page  displays only kits  known to support SBSv2.</p>

    68 		  <li> Click Next to select the recognized SDKs and Build Configurations to be created for this project

    69 		      <blockquote>

    70 		          <p>The SDKs and Build Configurations shows a tree of

    71 		              the SDKs that are available to be used, and for each SDK, the type of build configurations

    72 		              that are available. You can select a single SDK if you are developing the program

    73 		              for just one version of a platform, or multiple SDKs if your

    74 		              program is to be built against multiple platforms or operating system

    75 		              versions.</p>

    76 	          </blockquote>

    77          </li>

    78      </ol>

    79      <blockquote>

    80          <p class="note"><b>NOTE</b> The platforms listed are dependent upon the filter settings in the <a href="sdks/sdk_platform_filter.htm">Platform Filtering Preferences</a>.</p>

    81          <p><img src="../reference/images/import_bld_inf_03.png" alt="Symbian OS SDKs page" width="573" height="550"></p>

    82      </blockquote>

    83      <ol>

    84          <li value="5"> Click Next to select the mmp and extension make files

    85              <div class="Figure">

    86                  <p>One MMP file must be selected in order to continue. If the bld.inf file contains more than three MMP files, just select the MMP files you need to import. If there are three or less MMP files, then all are selected for importing.</p>

    87                  <p class="Image"><img src="../reference/images/import_bld_inf_04.png" alt="" width="573" height="550"  border="0" /></p>

    88              </div>

    89                  </li>

    90          <li>Click Next to enter the Project name and root directory</li>

    91          <p>When creating a project, project files are created in the root directory. Carbide.c++ creates additional files for each project. They consist of:</p>

    92          <ul>

    93              <li>.project - an xml file that provides a project description </li>

    94              <li>.cproject - an xml file that provides additional project information </li>

    95              <li>.settings folder - contains files that provide build configuration and preference settings </li>

    96                      </ul>

    97          <p>The root directory is a path to the root of your project. All necessary tool components, developer libraries, and information about the SDK are stored in subdirectories under this root. The whole path leading to the SDK root directory must be declared to the Windows system via the Environment Variables settings. The variable name is <span class="code">EPOCROOT</span> and the variable value is the full path where a Symbian OS SDK is installed in the Windows system.</p>

    98          <p>The root directory should contain all project related files that you want to work with in Carbide. The default directory is calculated by parsing the bld.inf file and mmp file(s).</p>

    99          <p class="Image"><img src="../reference/images/import_bld_inf_05.png" alt="" width="573" height="550"  border="0" /></p>

   100          <li> Click Finish to import the project

   101              <p>

   102                  The

   103                  wizard creates the project in the <a href="../reference/view_cpp_projects.htm">Project Explorer</a> view, where it can be built and edited as normal. If the wizard is unable to read the project files, then the page

   104                  describes the error that occurred. If an error occurs, you must fix the project file, and then

   105              re-import the bld.inf.</p>

   106                      </li>

   107      </ol>