You need to specify the source lookup path in terms of the compilation path and the local file-system path for the newly imported executable file. The CodeWarrior debugger uses both of these paths to debug the executable file. The compilation path is the path to the original project that built the executable file. If the original project is from an IDE on a different computer, you specify the compilation path in terms of the file system on that computer. The local file-system path is the path to the project that the CodeWarrior IDE creates in order to debug the executable file. Path mappings can be added per launch configuration or global, per workspace. In the latest case the mapping will be valid for all the projects within the workspace.
To add a path mapping to a launch configuration:
The corresponding page appears.
The Add Source dialog box appears.
The Path Mappings dialog box appears.
For example, the computer on which you debug the executable file is not the same computer that generated that executable file. On the computer that generated the executable file, the path to the parent project is D:\workspace\originalproject. Enter this path in the Compilation path text box.
Suppose the computer on which you debug the executable file is not the same computer that generated that executable file. On your current computer, the path to the parent project of the executable file is C:\projects\thisproject. Enter this path in the Local file system path text box.
The Path Mappings dialog box closes. The mapping information now appears under the path mapping shown in the Source Lookup Path list of the Source page.
The IDE searches the paths in the order shown in the Source Lookup Path list, stopping at the first match. To change this order, select a path, then click the Up or Down button to change its position in the list.
The IDE saves your changes.