Tutorial: Ready to Build/Analyze

JavaScript is not currently enabled, but is required for full CodeSonar manual search and browse functionality.

If you are viewing this file in your hub's Web GUI, enable JavaScript in your browser: you will also need it for GUI functionality.

If you opened this file directly from disk, your browser may be directly suppressing JavaScript functionality: certain browsers perform this suppression on local files (but not files delivered by web servers) for security reasons.

If you access the manual through the hub's Web GUI, the functionality will not be suppressed because the hub is a web server.
Alternatively, your browser may allow you to explicitly disable the security setting that suppresses functionality. See the CodeSonar FAQ for more information.

CodeSonar^® 9.2p0

CONFIDENTIAL

CodeSecure Inc

Tutorial: Ready to Build/Analyze

C and C++

When CodeSonar is used to analyze C and C++ source code, it constructs a CodeSonar project by observing the normal software build process and identifying compiler calls. Each time CodeSonar recognizes one of these calls it updates the project definition to incorporate the information about the C and C++ source files that were compiled, with compiler-specific behavior and the effects of compiler flags taken into account.

We provide instructions for building a CodeSonar project based on various standard build techniques applied to a sample source file. You can experiment by trying several of the available build techniques, or just choose one to perform and then go on with the remainder of the tutorial.

Java

The CodeSonar build of a Java project is performed after the normal build. It collects the Java bytecode files produced by the normal build, along with the corresponding Java source code for any parts of the project for which warnings are required. (This is significantly different from the way in which CodeSonar builds a C/C++ project.)

The CodeSonar build of a C# project is performed after the normal build. It collects the C# bytecode files produced by the normal build, along with the corresponding C# source code for any parts of the project for which warnings are required. (This is significantly different from the way in which CodeSonar builds a C/C++ project.)