What If I Have No Compiler?

CodeSonar ships with a "null compiler" executable, allowing users without compilers to build CodeSonar projects.

• How it Works
• Building Without A Compiler
• Note: Projects with System Include Files

How it Works

The CodeSonar installation includes an executable called null-cc. The null-cc executable is not a compiler, but you can use it in place of a compiler to build your project. CodeSonar will (by default) use the xcc compiler model for projects built with null-cc.

Both C and C++ projects can be built using this technique.

Building Without A Compiler

To build without a compiler:

1. Make sure that $CSHOME/csurf/bin is in your PATH.
2. Use null-cc in place of a compiler name in the build process.

Examples

• Build file myfile.c into a project called myproj:
  codesonar analyze myproj null-cc myfile.c
• Build a project called myproj based on a makefile that refers to null-cc:
  codesonar analyze myproj make mytarget
• Build a project called myproj based on a makefile that uses variable CC to denote the name of a C compiler:
  codesonar analyze myproj make CC='null-cc' mytarget

Note: Projects with System Include Files

Most "real" software projects make use of system include files. Such files are usually installed as part of a compiler package, so they may not be present on systems that lack a compiler.

Obtaining Include Files

If your project needs system include files and there are none currently available on your system, you will need to install some before building the project. Consult your system administrator to determine and locate the best include files for your project and computer system.

Building with Include Files

Once system include files are installed, specify their location(s) in the project configuration file.

For example, to use include files from directory /my/include/files:

CFLAGS_APPEND += --sys_include /my/include/files