 |
|
 |
RENESAS TOOL NEWS on October 16, 2004: RSO-HEW_2-041016D
A Note on Using Integrated Development Environment High-performance Embedded Workshop
--On Installing More Than One C/C++ Compiler
for the SuperH RISC engine Family CPUs--
|
Please take note of the following problem in using the High-performance Embedded Workshop, an integrated
development environment:
- If the version 9.00 Release 00 of a C/C++ compiler package for the SuperH
RISC engine family (hereafter abbreviated to SH C) is installed in the PC
where any one or more of its versions 5.1 through 6.0C reside, the High-performance Embedded Workshop
can create no project workspaces for the SH C's earlier version.
- Products Concerned
The High-performance Embedded Workshop V.3.01.06 included with the following compiler package:
C/C++ Compiler package V.9.00 Release 00
(used for the SuperH RISC engine family)
- Description
The High-performance Embedded Workshop can create no project workspaces for any of the SH C V.5.1
through V.6.0C; that is, you cannot select any of those in the
Project Workspace window even if you go through the following steps:
| (1) | Consider any one or more of the SH C V.5.1 through V.6.0C and the SH C V.9.00 R00 have already been installed both in the host PC. |
| (2) | Launch the High-performance Embedded Workshop included with the SH C V.9.00 R00. |
| (3) | Open the Tools menu and select the Administration command. The Tool Administration dialog box appears. |
| (4) | Click the Register button to register the hrf file for the SH C V.5.1 through V.6.0C in this dialog box. |
- Workaround
If you want to create project workspaces for any of the SH C V.5.1
through V.6.0C using the High-performance Embedded Workshop V.3.01.06, update this to the problem-fixed
High-performance Embedded Workshop V.3.01.06. The problem-fixed High-performance Embedded Workshop can be downloaded from HERE.
NOTICE:
| | Be sure to update your product to the problem-fixed one because it
contains the file necessary for fixing the problem though it and the
product concerned have the same version number of V.3.01.06. |
- Schedule of Fixing the Problem
We plan to fix this problem in our next release of the compiler package.
|
 |