Description
When copying or archiving an APM project (.apj) file, the copied project may sometimes not re-build as expected, in particular, if the project contains source files which have been added from different directories or a drive/volume belonging to a different developer. This is because of the way APM stores the paths to the files in the project - sometimes absolute, sometimes relative paths.

Solution
Files are normally added with paths relative to the location of the project. A system variable $$DepthOfDotAPJBelowProjectRoot lets you control how deep in a directory tree the project file is. Files are added with absolute paths if above this point, or on a different drive/volume.

Therefore, to allow the project tree to be copied recursively to another location whilst retaining the project structure, and for the project to continue to work at its new location, you must set $$DepthOfDotAPJBelowProjectRoot appropriately.

See section 3.3.5.2 of Application Note 46, Editing Project Templates in the ARM Application Notes.

Note that there is a known problem with applying the $$DepthofDotAPJBelowProjectRoot variable. The value you enter for this is saved as part of the project, however, after you reload the project, you must manually re-apply the value (even though the right value can be seen in the Edit Variables dialog). If this is not done, the paths used by the debugger will be wrong, causing problems carrying out source level debugging. This is fixed in SDT 2.51