U. freescale IDE 5.7

PDF

Dokument

Reklamë

Preference and Target Settings Options

Target Name

Use the Target Name text box to set or modify the name of the current build target. This name appears in the Targets view in the Project window. This name is not the name assigned to the final output file, that is set in the Linker panel for the build target.

Type

Choose from the Type options the desired source-tree path type:

• Absolute Path—This source-tree type is based on a file path.

• Environment Variable—This source-tree type is based on an existing environmentvariable definition. The Macintosh-hosted IDE cannot create or modify this sourcetree type.

• Registry Key—This source-tree type is based on an existing Windows registry key entry.

U

Update data every

seconds

Select this option to update the information displayed in debugging-session windows after a specified time interval. Enter the number of seconds n to elapse before the next update.

Clear this option to prevent data updates and keep the same window information throughout the debugging session.

Use Concurrent Compiles

Select the Use Concurrent Compiles option to run more than one compiling process at a time. Concurrent compiling makes better use of available processor capacity by allowing the operating system to optimize resource utilization, such as taking advantage of overlapped input/output.

Both single- and multi-processor systems benefit from enabling concurrent compiles. On multiprocessor systems, the speed-up is significant.

Use Debugging Monitor

Select the Use Debugging Monitor option to view debugging windows on a second monitor after a debugging session starts. This option only appears when the second monitor is connected to the computer.

IDE 5.7 User’s Guide 447

Preference and Target Settings Options

Use default workspace

Select this option to have the IDE use the default workspace. The IDE uses the default workspace to save and restore window and debugging states from one session to the next.

For example, if you select this option and close the IDE with a project window visible onscreen, that project window reappears the next time you start the IDE.

Clear this option to have the IDE start with the same default state for each new session: no windows visible onscreen.

For example, if you clear this option and close the IDE with a project window visible onscreen, that project window does not appear the next time you start the IDE. Instead, the

IDE always starts without opening any windows.

Use External Debugger

Select this option to have the IDE use an external debugger application in place of the

CodeWarrior debugger.

Use External Editor

Select the Use External Editor option to use an external text editor to modify text files in the current project. Clear the option to use the text editor included with the IDE.

Use Local Project Data Storage

Select the Use Local Project Data Storage option to store (on the host computer) data associated with a project file on a read-only volume. Clear the option to store project data inside the same folder as the project file itself.

After loading a project file, the IDE creates or updates an associated project data folder.

The IDE stores intermediate project data in this folder. When building or closing a project, the IDE uses the information in the project data folder to update the project file.

By default, the IDE places the project data folder within the same folder as the project file.

However, the IDE cannot create or update a project data folder in a location that grants read-only privileges.

If you are creating one project to be accessed by multiple users that are running

CodeWarrior on separate machines, then each user should select this option to create a local data storage folder for the shared project. The folder containing the project file should be set to read-only. This will cause the target information to be stored locally on each user’s machine, instead of inside a folder next to the project file.

448 IDE 5.7 User’s Guide

Preference and Target Settings Options

Use modification date caching

Use the Use modification date caching option to determine whether the IDE checks the modification date of each project file prior to making the project. The settings include:

• enabled–the IDE caches the modification dates of the files in a project. At compilation time, the IDE refers to this cache to determine whether a specific file should be recompiled. This can shorten compilation time significantly for large projects.

• disabled–the IDE checks every file at each recompile of the project. Use this setting if using third-party editors to ensure that the IDE checks every file at compilation time.

Use Multiple Document Interface

Toggle this option to change the IDE interface:

• Selected—The IDE uses MDI (Multiple Document Interface). In this interface, the

IDE uses a main application window with a gray background. IDE windows appear inside the main application window. The gray background obscures your view of the desktop.

• Cleared—The IDE uses FDI (Floating Document Interface). In this interface, the

IDE does not use a main application window. You can see through the IDE user interface to your desktop. IDE windows appear above the desktop.

Use multiple undo

Select the Use multiple undo option to remember several undo and redo operations in editor windows. Clear the option to remember only the most recent undo or redo action.

The IDE stores undo and redo actions on a stack in first-in last-out (FILO) order, however, the stack size and capability are limited. For example, assume there are five undo actions on the stack (ABCDE). If the IDE redoes two actions (ABC), then performs a new action

(ABCF), the undo events (DE) are no longer available.