Keil Logo

Create a Library File

Select Create Library in the dialog Options for Target — Output. µVision3 will call the Library Manager instead of the Linker/Locater. Since the code in the Library will be not linked and located, the entries in the Linker options dialogs are ignored. Also the CPU and memory settings in the Target page are not relevant.

Once you have created a library file, you may add this library file to another project just in the same way as you add source files to a project. µVision3 automatically detects the file type as library file. Typically this is all you need to do to work with a library. In some rare cases it might be required to select specific library files that should always be included.


  • If you plan to use the library on different directives, you should select a CPU listed under Generic in the µVision3 Device Database™, for example Generic — ARM7.
  • For C166: Check if you need to enter a Target — Data Threshold value in the options dialog.
  • For C166: The directive NOFIXDPP should be entered under Options — C166 — Misc, if the library is designed for applications with one of the following configurations:
    • More than 16KB ROM or 16KB ROM are set for Target — Near Memory. In this case the L166 DPPUSE directive will be applied. This directive requires that the C166 compiler makes no default assumptions for the DPP registers.
    • The User Stack is set to the memory class SDATA or IDATA. You may use the C166 directive USERSTACKDPP3 instead of NOFIXDPP, but NOFIXDPP is more generic since no DPP register assumptions are made.
  Arm logo
Important information

This site uses cookies to store information on your computer. By continuing to use our site, you consent to our cookies.

Change Settings

Privacy Policy Update

Arm’s Privacy Policy has been updated. By continuing to use our site, you consent to Arm’s Privacy Policy. Please review our Privacy Policy to learn more about our collection, use and transfers
of your data.