Tool News
 
 
 

Tool News

Products Info
Downloads
Tools FAQs
RENESAS TOOL NEWS on June 16, 2005: RSO-HEW_2-050616D

A Note on Using the High-performance Embedded Workshop V.4
--On Using Custom Placeholders--

Please take note of the following problem in using the High-performance Embedded Workshop V.4, an integrated development environment:
  • On using custom placeholders

  1. Versions Concerned
    High-performance Embedded Workshop* V.4.00.00 and V.4.00.01

    The High-performance Embedded Workshop is bundled with the software products (a C compiler and others) that support it.

    To check for the version number of your High-performance Embedded Workshop, open the Help menu and select the About High-performance Embedded Workshop command.


  2. Description
    If the name of a custom placeholder* is used as an option parameter of the linker or library generator, the name cannot be converted to the path name at build, which results in an error.

    The steps for defining the name of a custom placeholder are explained below. Such a name that is defined by following these steps can be used as an option parameter, $(PROJDIR), for example. (Here $(PROJDIR) is the name of a placeholder predefined in the High-performance Embedded Workshop).

    (1) Open the Setup menu and select the Customize command. The Customize dialog box appears.
    (2) Click the Placeholders tab; then click the Add button on the right of the Application wide custom placeholders or Workspace wide custom placeholders list box. You see the New Custom Placeholder dialog box.
    (3) In this dialog box, enter an appropriate name and an annotation of the placeholder into the Placeholder and Description text boxes respectively.
    (4) Click the Browse button* and select the directory to associate with the placeholder in the Select Directory dialog box.

    This button is on the right of the Directory text box in the New Custom Placeholder dialog box.



  3. Conditions
    This problem occurs if the product concerned is used together with any of the following compiler packages:

    (1) C/C++ compiler package for the SuperH RISC engine family
    (2) C/C++ compiler package for H8, H8S, and H8SX families
    (3) C compiler package for the M32R family--M3T-CC32R
    (4) C compiler package for the M32C/90, M32C/80, M16C/80, and M16C/70 series--M3T-NC308WA
    (5) C compiler package for the M16C/60, M16C/30, M16C/20, M16C/10, M16C/Tiny, and R8C/Tiny series--M3T-NC30WA
    (6) C compiler package for the R8C/Tiny series (freeware)--M3T-NC8C*

    The M3T-NC8C has been merged into the evaluation version of the M3T-NC30WA. If you are using the former, update it to the latter, in which this problem arises, however.



  4. Workaround
    Don't use the name of any custom placeholder as an option parameter of the linker or library generator.


  5. Schedule of Fixing the Problem
    We plan to fix this problem in the next release of the product.




© 2008. Renesas Technology Corp., All rights reserved. Privacy | Legal