8.4.4. Code Warrior¶
8.4.4.1. Axivion Eclipse Plugin is installed but does not appear¶
Eclipse checks dependencies before loading a plugin. If the dependencies of a plugin are not fulfilled, Eclipse silently skips loading it rather than producing a runtime error.
Code Warrior bundles its own JRE, which often seems to be JRE 6 and therefore too old for the Axivion Eclipse Plugin. In such cases, Eclipse silently does not load the Axivion Eclipse Plugin (see Axivion Eclipse Plugin Requirements).
8.4.4.2. Replacing the JRE of Code Warrior¶
In the Code Warrior installation directory, there should be a folder
eclipsejre containing the JRE used by Code Warrior.
To replace the JRE, rename jre to jre.bak and place your desired JRE in
eclipsejre. It may be sufficient to simply rename the bundled JRE; in that case, the
system JRE will be used.
8.4.4.3. Configuring the Build Process with cafeCC¶
8.4.4.4. Legacy Codewarrior¶
Very old Codewarrior IDEs (non-Eclipse-based) use a proprietary build
system that cannot be modified from outside the IDE itself.
Therefore, it is necessary to run the code analysis with cafeCC via a script by
manually defining the calls. Proceed as follows:
In the IDE, navigate to
Edit→Settings(Alt-F7), then toCompiler forandLinker for, and check the box “display generated command line in message window”.Run the native build.
Copy the output from the native build’s protocol window and paste it into a text editor.
Replace the calls to the native compiler with calls to
cafeCC.