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.

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.
  - 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.

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.

The Ounce/Make utility provides a command line interface for generating AppScan® Source project files (.ppf) from makefiles (a makefile provides a means to build an executable application or library from source files). The generated ppf files contain all of the information needed by AppScan® Source to assess the source code that the corresponding makefile is responsible for compiling. Once Ounce/Make generates the .ppf files, you can import or add the project files into AppScan® Source.

To launch the utility:

On Windows™ systems, run <install_dir>\bin\ouncemake.exe (where <install_dir> is the location of your AppScan® Source installation), for example on Windows™ (32-bit):
```
C:\Program Files\IBM\AppScan Source\bin\ouncemake.exe
```
On Linux™ systems, run <install_dir>/bin/ouncemake, for example:
```
/opt/ibm/appscansource/bin/ouncemake
```

Make is the tool that automates compiling, linking (and so forth), of programs, taking into account the interdependencies of modules and their modification times. Make reads instructions from a makefile, which specifies a set of targets to build, the files on which they depend, and the commands to execute to produce them.