 |
|
|
MESC TOOL NEWS:
MESCT-CC32R-990916D
CC32R V.2.00 Release1
Precaution
|
|---|
Please take note of the following problem in using cross-tool kit CC32R for the M32R family of microcomputers.
- Versions Concerned
Windows 98/95 versions only of CC32R V.2.00 Release1
- Problem
If an output directory is changed by using the "Environment" -> "Project Settings..." -> "TARGET" -> "Output Directory" command in the integrated development environment (TM), the "cannot openfile ..." error occurs at linking.
Note that this problem does not arise if TM is not used or output directories are not changed.
- Workaround
Change an output directory after modifying the LIB32R\CC32R.MKT file as shown below by an editor, for example, and restart TM. The LIB32R\CC32R.MKT file is found in the directory where CC32R has been installed.
Note that only the line indicated below is allowed to be modified because the LIB32R\CC32R.MKT file is a system file.
After modifying CC32R.MKT file
--------------------------------------------------------------------
|
| Line 59 [CMDFILE] {
| Line 60 1="$(MRLFLAGS) %FLAGS% "
| Line 61 20="%OUTDIR%\\%FILE_NNS%.%EXT_I% " <-Modified
| Line 62 }
|
--------------------------------------------------------------------
Before modifying CC32R.MKT file
--------------------------------------------------------------------
|
| Line 59 [CMDFILE] {
| Line 60 1="$(MRLFLAGS) %FLAGS% "
| Line 61 20="%FILE_NNS%.%EXT_I% "
| Line 62 }
|
--------------------------------------------------------------------
|
|
