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.
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.
Running Ounce/Make
You can run Ounce/Make from any directory where a make command executes successfully. In most cases, the ouncemake executable is not in the directory where you invoke it. Therefore, it is recommended that you add the directory that contains ouncemake to the PATH environment variable to invoke ouncemake easily.

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.
    - Running Ounce/Make
      You can run Ounce/Make from any directory where a make command executes successfully. In most cases, the ouncemake executable is not in the directory where you invoke it. Therefore, it is recommended that you add the directory that contains ouncemake to the PATH environment variable to invoke ouncemake easily.
    - Naming project files
      Ounce/Make uses conventions outlined in this topic to name AppScan® Source project files.
    - Ounce/Make output
      While running, Ounce/Make generates output informing you of certain events.
  - 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.
  - 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.

Running Ounce/Make

You can run Ounce/Make from any directory where a make command executes successfully. In most cases, the ouncemake executable is not in the directory where you invoke it. Therefore, it is recommended that you add the directory that contains ouncemake to the PATH environment variable to invoke ouncemake easily.

For example, if your source code and/or makefile reside in the directory \development\srcdir, to run ouncemake you must first change to that directory:

%cd \development\srcdir

and then run ouncemake:

%ouncemake <options>

Note: For backward compatibility, the pmake command is still accepted. However, pmake may be removed in a future release.