Upgrading Configuration Files

• Patching Configuration Files
• The Patch Files

If you are upgrading CodeSonar, use the following table to determine whether you need to update any of your configuration files.

Note that you need the patch tool that works with the unified diff format. See Wikipedia: Patch (Unix) for more information about the patch tool.

Patching Configuration Files

We have provided patch files to enable you to update old configuration files for use with the latest version of CodeSonar. To apply the changes:

1. Save a copy of the appropriate patch file in the same directory as the configuration file you wish to update.
2. Change the name of the patch file to fname.conf.patch, where fname.conf is the name of the configuration file.
3. Edit the first two lines of the patch file to refer to fname.conf.
4. Run the patch command:
   patch -p0 < fname.conf.patch
5. If patch reports any conflicts, go through fname.conf.rej manually and decide, for each conflict, whether to use the text from your original file or from the patch.
   • Once you have decided, copy and paste the relevant text into the updated configuration file.
   • If the conflict only involves file comments, using the text from the patch will make your next upgrade easier.

Per-Compiler → Compiler Template

If you created per-compiler configuration files to use with an earlier version of CodeSonar, you will need to integrate them with the appropriate compiler configuration file templates.

Before upgrading CodeSonar:

1. Identify your old per-compiler configuration files, if any. They will have paths of the form $CSONAR/csurf/compiler_confs/ compilername.conf.
2. Save copies of the per-compiler configuration files.

Once you have upgraded CodeSonar, do the following for each old per-compiler configuration file C.conf.

1. Determine which of the new compiler configuration file templates in $CSONAR/csurf/compiler_confs/ corresponds to C.conf.
   • Identify the language(s) L and target address size(s) S for which the settings in C.conf are designed.
   • Be aware that it may correspond to multiple compiler configuration file templates C.L.S.conf.
2. Compare the settings in C.conf to the settings in the new template(s) you identified in the previous step.
   diff C.conf C.L.S.conf
   If there is no difference, you can discard C.conf. No integration is necessary.
3. If there are differences, you may need to edit the new template(s) C.L.S.conf.
4. • If a parameter P has different settings in the two files and you prefer the setting in C.conf, change the setting for P in C.L.S.conf accordingly.
   • If a parameter P is set in C.L.S.conf but not in C.conf, we recommend leaving the setting alone.
   • If a parameter P is set in C.conf but not in C.L.S.conf, check that P is a valid compiler-dependent parameter. If it is, and you determine that the setting is suitable, add it to C.L.S.conf.

The Patch Files

The patch files currently available are listed in the following table.