Home
Reference
Review reference information for the product.
The Ounce/Make build utility
Ounce/Make is a tool that automates the importing of configuration information into AppScan® Source from build environments that use makefile. Ounce/Make eliminates the need to import configuration information from makefiles manually; this the recommended method of configuring these projects.
Ounce/Make properties file
The Ounce/Make Properties file (ouncemake_properties.xml) is an XML file that contains details about your build environment. When Ounce/Make runs, it finds the properties file based on the search path or the -p option. The properties file must specify the compiler used in your build environment, the linker, and make elements.
Ouncemake properties file elements
OuncemakeProperties, the root element of the Properties file, contains the elements that are listed in this topic.
FileOptions
The FileOptions element allows include paths, macros, and other compiler options to be specified for files with a particular extension. You can use FileOptions multiple times to specify different options for files with different extensions. For example, as shown below, if you have a project that contains both C and C++ files, create two FileOptions elements, one for each file type.

Reference
Review reference information for the product.
- The Ounce/Make build utility
  Ounce/Make is a tool that automates the importing of configuration information into AppScan® Source from build environments that use makefile. Ounce/Make eliminates the need to import configuration information from makefiles manually; this the recommended method of configuring these projects.
  - Requirements
    To create AppScan® Source project files successfully, you must run Ounce/Make in a suitable environment. The following list itemizes the requirements for Ounce/Make to run successfully. If you do not meet all of these requirements, Ounce/Make fails.
  - What Ounce/Make supports
    Ounce/Make supports multiple computer platforms, compilers, and make versions.
  - Operation
    Ounce/Make operates with your Make to extract the necessary configuration information from your makefiles and create appropriate AppScan® Source project files (ppf). To accomplish this, Ounce/Make requires that you provide certain information about the build environment, such as the make version used.
  - Ounce/Make command syntax and make options
    Ounce/Make supports multiple options that can change the way it behaves when it runs.
  - Ounce/Make properties file
    The Ounce/Make Properties file (ouncemake_properties.xml) is an XML file that contains details about your build environment. When Ounce/Make runs, it finds the properties file based on the search path or the -p option. The properties file must specify the compiler used in your build environment, the linker, and make elements.
    - Ouncemake properties file elements
      OuncemakeProperties, the root element of the Properties file, contains the elements that are listed in this topic.
      - Compiler
        The Compiler element specifies the compiler executable used in your build environment. The value of this element must be an absolute path to an executable. This element consists of one optional attribute, macro, which specifies the name of the variable that stores the compiler executable when building and a value specific to the path to the compiler. If you do not specify the macro attribute, Ounce/Make sets the macro attribute to CC by default. The Properties File can contain multiple Compiler elements, but at least one is required.
      - Linker
        The Linker element specifies a linker executable used in the build environment. The value of this element must be an absolute path to an executable. The Properties File can contain multiple Linker elements, but at least one is required.
      - Make
        The Make element specifies a make executable used in your build environment. The value of this element must be an absolute path to an executable. The Properties File can contain multiple Make elements, but at least one is required.
      - MakeOptions
        The MakeOptions element specifies the options to pass to the make executable. This element is optional and cannot appear more than once in the Properties File.
      - Options
        The Options element specifies options to pass to Ounce/Make upon invocation.
      - GlobalProjectOptions
        The GlobalProjectOptions element specifies Project level options for all files contained within the project. The GlobalProjectOptions element and its attributes are not required.
      - FileOptions
        The FileOptions element allows include paths, macros, and other compiler options to be specified for files with a particular extension. You can use FileOptions multiple times to specify different options for files with different extensions. For example, as shown below, if you have a project that contains both C and C++ files, create two FileOptions elements, one for each file type.
      - Executable
        The Executable element allows use of any executable (other than compiler, linker, or make) in the build environment. The value of this element must be an absolute path to an executable. The Executable element contains one attribute, macro, which specifies the name of the variable used to store the executable name when building. The value for the macro attribute must be unique across all Executable elements.
      - MountRoot
        The MountRoot element is required if you are assessing source code from a remote system. MountRoot tells Ounce/Make to pre-pend the specified mount point to all absolute include paths that it encounters.
    - Sample properties files
  - Examples
    This section describes three ways to use Ounce/Make.
- AppScan® Source command line interface (CLI)
  The CLI is an interface to core AppScan® Source functionality.
- The Ounce/Ant build tool
  This section describes how to use Ounce/Ant, an AppScan® Source build utility that integrates AppScan Source and Apache Ant. Integrating Ounce/Ant with your Ant environment helps you automate builds and code assessments.
- AppScan® Source Data Access API
  The Data Access API provides access to AppScan® Source-generated assessment results, including findings and finding details. It also provides access to assessment metrics such as analysis date and time, lines of code, V-density, and number of findings.
- Glossary
  Learn common product terminology.

`FileOptions`

The FileOptions element allows include paths, macros, and other compiler options to be specified for files with a particular extension. You can use FileOptions multiple times to specify different options for files with different extensions. For example, as shown below, if you have a project that contains both C and C++ files, create two FileOptions elements, one for each file type.

The following list describes the attributes for the FileOptions element:

extensions: String value. Semicolon-separated list of file extensions. Every file with an extension that matches an extension in this list acquires the options specified by this property. If a file extension applies to more than one occurrence of the FileOptions property, then the first occurrence in the Ounce Make properties file takes precedence.
compiler_options: String value. List of compiler options, separated by a space, to apply to all files with the specified extension. Do not specify include paths and macros here.
include_paths: String value. Semicolon-separated list of include paths to apply to all files with the specified extension.
macros: String value. Semicolon-separated list of macros to apply to all files with the specified extension.

Examples

The following FileOptions examples show how to configure the Ounce Make properties file to apply the correct options to both C and C++ files.

The FileOptions element with extensions="c" applies its other attribute values only to files with a c extension <filename.c>. The FileOptions element with extensions="cpp;cxx" will apply its other attribute values only to files with cpp (<filename.cpp>) or cxx (<filename.cxx>) extensions.

<!-- g++ options for C files -->
<FileOptions
	extensions="c"
	compiler_options="-gcc_linux_i386"
	include_paths="/usr/local/include;
	/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/include;
	/usr/include"
	macros=""/>

<!-- g++ options for C++ files -->
	<FileOptions
	extensions="cpp;cxx"
	compiler_options="-g++_linux_i386"
	include_paths="/usr/include/c++/3.2.3;
	/usr/include/c++/3.2.3/i386-redhat-linux;
	/usr/include/c++/3.2.3/backward;/usr/local/include;
	/usr/lib/gcc-lib/i386-redhat-linux/3.2.3/include;
	/usr/include"
	macros="__GNUG__=3" />

Description

extensions="c" and extensions="cpp;cxx"

specifies the file extensions for which these file options apply.