Handling non-standard or unsupported keywords: Difference between revisions
No edit summary |
|||
Line 1: | Line 1: | ||
Many target compilers for specific systems support specialized non-standard keywords. Although the STRIDE compiler recognizes and accepts most of them, sometimes one is unsupported. This article describes how to handle this. | |||
If an unrecognized keyword in your source file is preventing compilation in STRIDE, you can work around the issue by creating an explicit empty definition (ie macro) for the keyword within STRIDE Studio. | |||
For example if | To create a new definition, from the Studio menu, choose ''Workspace/Settings'', then choose the ''Compiler'' tab and add a preprocessor definition for the unrecognized keyword. | ||
For example if your source contains a keyword <tt>__inline__</tt> that is not supported by STRIDE and is preventing successful compilation, then you remedy this by adding <tt>'__inline__='</tt> to the workspace preprocessor definitions. | |||
[[Category:Troubleshooting]] | [[Category:Troubleshooting]] | ||
[[Category:Compiler]] | [[Category:Compiler]] |
Revision as of 15:15, 30 September 2008
Many target compilers for specific systems support specialized non-standard keywords. Although the STRIDE compiler recognizes and accepts most of them, sometimes one is unsupported. This article describes how to handle this.
If an unrecognized keyword in your source file is preventing compilation in STRIDE, you can work around the issue by creating an explicit empty definition (ie macro) for the keyword within STRIDE Studio.
To create a new definition, from the Studio menu, choose Workspace/Settings, then choose the Compiler tab and add a preprocessor definition for the unrecognized keyword.
For example if your source contains a keyword __inline__ that is not supported by STRIDE and is preventing successful compilation, then you remedy this by adding '__inline__=' to the workspace preprocessor definitions.