 |
|
|
MESC TOOL NEWS:
MESCT-TM-001016D
- Please take note of the following problems in using integrated development environment TM:
- On scanning the dependencies of header files on the source file
- On adding files to the project
- On Performing build
-
Versions Concerned
TM V.3.00 -- V.3.01 for NC308WA, NC30WA, and NC79WA
-
Problem on Scanning Dependencies of Header Files on Source File
- 2.1 Description
- Even if any header file included in the C source file has already been deleted, scanning the dependencies of header files on the source file by ProjectEditor in TM cannot remove the header file's name concerned from the project.
- 2.2 Conditions
- This problem occurs if the following two conditions are satisfied:
- (1) Any header file included in the C source file is deleted or commented out.
- (2) Then, the C source file is scanned by ProjectEditor in TM to update the dependencies of header files on it.
- 2.3 Workaround
- Delete files unnecessary for the project by selecting [Project] --> [Delete] menu in ProjectEditor.
- 2.4 Schedule of Fixing Problem
- We plan to fix this problem in our next release.
TM Precaution
MESCT-TM-001016D
-
Problem on Adding Files to Project
- 3.1 Description
- When adding a file other than a C source file (for example, a header or library file) to the project, the path to the file is fixed in the working directory, resulting in the user-specified path being invalid.
- 3.2 Condition
- This problem occurs if any file other than a C source file is added to the project.
- 3.3 Workaround
- To add a header file, make an automatic entry by scanning the dependency of it on the source file using ProjectEditor in TM. To add any other file than header files, do once and close the project; then, edit the contents of the project file (with extension ".tmk") by an editor and so on.
- 3.4 Schedule of Fixing Problem
- We plan to fix this problem in our next release.
TM Precaution
MESCT-TM-001016D
-
Problem on Performing Build
- 4.1 Description
- Even if a compile error arises, build is performed without stopping until linking is complete. However, link errors will be detected because compilation is improperly terminated.
- 4.2 Condition
- This problem occurs if any of the assemble command options, for example, -as30, is used as an option for compilation.
- 4.3 Workaround
- Should build not stop running even after a compile error arises, cancel the build by selecting [Action] --> [Cancel Build] menu.
- 4.4 Schedule of Fixing Problem
- We plan to fix this problem in our next release.
|
|
