|
|||||||||||
Technical Support On-Line Manuals µVision User's Guide ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() |
Project Targets and File GroupsThe uVision IDE, especially the Project Window, control the options and organization of a project.
Most examples delivered with µVision have targets configured for various application setups. Project Target Selector: You can switch to another project target using the drop-down in the toolbar. (More on creating project targets below).
File groups have no influence on the build process. Create file groups and project targets using the menu Project — Manage — Project Items... — Project Items. Refer to Create file groups
Files belonging to those groups cannot be moved, nor can you add your own source files to those groups. However, you can set Options for Components and you can add code to the files that are not read-only. Options for project targets and groups can be set using the Project Window. | ||||||||||
|
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.