3.4.1 - Using com.castsoftware.cpp 3.0
Overview
This release of CAST Imaging (3.4.1-funcrel) introduces support for analyzing C, C++ and Pro*C using a new 3.0.0 release of the com.castsoftware.cpp extension. To use this new extension with CAST Imaging v3, some specific steps are required, which are detailed below.
Step 1 - Ensure CAST Imaging Core 8.4.5 is installed
com.castsoftware.cpp requires com.castsoftware.imaging.core 8.4.5 or above. Ensure this is release is installed on your analysis node(s). Note that for Linux/Docker installations, com.castsoftware.imaging.core 8.4.5 is bundled with CAST Imaging 3.4.1-funcrel.
Step 2 - Update Extension Stategy in the UI
com.castsoftware.cpp is released initially as a beta, therefore the Extension Strategy stability level will need to be updated to allow the automatic install of “beta” extensions when C/C++/Pro*C source code is delivered for analysis.
Step 3 - Whitelist/un-deny the com.castsoftware.cpp.missingtable extension
Exceptionally the 3.4.1-funcrel release of CAST Imaging blacklists/denies the com.castsoftware.cpp.missingtable to prevent its auto-installation when delivered source code contains C/C++/Pro*C related files without the accompanying SQL source code and the Extension Strategy stability level is set to “funcrel”. This is ensure that users that do deliver C/C++/Pro*C related files in amongst their other source code will not have results containing missing table objects. Therefore to ensure coherent results when using the com.castsoftware.cpp extension, the com.castsoftware.cpp.missingtable should be whitelisted/un-denied in the UI:
Step 4 - Deliver C/C++/Pro*C source code
Finally deliver the C/C++/Pro*C source code and SQL related source code as normal and proceed with the analysis. The com.castsoftware.cpp extension will be installed automatically and results can be consulted as normal.