11.07.2015 Views

MSP430 IAR C/C++ Compiler reference guide - Rice University

MSP430 IAR C/C++ Compiler reference guide - Rice University

MSP430 IAR C/C++ Compiler reference guide - Rice University

SHOW MORE
SHOW LESS
  • No tags were found...

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Getting startedThe way you set up a runtime environment and locate all the related files differsdepending on which build interface you are using—the <strong>IAR</strong> Embedded Workbench IDEor the command line.Choosing a runtime library in the <strong>IAR</strong> Embedded Workbench IDETo choose a library, choose Project>Options, and click the Library Configuration tabin the General Options category. Choose the appropriate library from the Librarydrop-down menu.Note that for the DLIB library there are different configurations—Normal, andFull—which include different levels of support for locale, file descriptors, multibytecharacters, et cetera. See Library configurations, page 47, for more information.Based on which library configuration you choose and your other project settings, thecorrect library file is used automatically. For the device-specific include files, a correctinclude path is set up.Choosing runtime environment from the command lineUse the following command line options to specify the library and the dependency files:Command lineDescription-I msp430\inc Specifies the include paths-I msp430\inc\{clib|dlib} Specifies the library-specific include path. Use clib ordlib depending on which library you are using.libraryfile.r43Specifies the library object file--dlib_configC:\...\configfile.hTable 2: Command line options for specifying library and dependency filesSpecifies the library configuration file (for the <strong>IAR</strong> DLIBLibrary only)For a list of all prebuilt library object files for the <strong>IAR</strong> DLIB Library, see Table 11,Prebuilt libraries, page 49. The table also shows how the object files correspond to thedependent project options, and the corresponding configuration files. Make sure to usethe object file that matches your other project options.For a list of all prebuilt object files for the <strong>IAR</strong> CLIB Library, see Table 22, Runtimelibraries, page 76. The table also shows how the object files correspond to the dependentproject options. Make sure to use the object file that matches your other project options.Part 1. Using the compiler9

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!