Jump to main content
HCL Logo Product Documentation
Customer Support Software Academy Community Forums
HCL AppScan Source
  • Welcome
  • Introduction to HCL® AppScan® Source
  • What's New in AppScan® Source
  • Installing
  • Configuring
  • Administering
  • Developing
  • Extending product function
  • Reference
  • Troubleshooting and support
  1. Home
  2. Reference

    Review reference information for the product.

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

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

  5. Ouncemake properties file elements

    OuncemakeProperties, the root element of the Properties file, contains the elements that are listed in this topic.

  • Welcome

    Welcome to the documentation for HCL® AppScan® Source.

  • Introduction to HCL® AppScan® Source

    HCL® AppScan® Source delivers maximum value to every user in your organization who plays a role in software security. Whether a security analyst, quality assurance professional, developer, or executive, the AppScan Source products deliver the functionality, flexibility, and power you need - right to your desktop.

  • What's New in AppScan® Source

    Explore these new features that have been added to AppScan® Source - and note any features and capabilities that have been deprecated in this release.

  • Installing

    Learn how to install the product.

  • Configuring

    Learn how to configure the product.

  • Administering

    Learn how to administer the product.

  • Developing

    Learn how to develop by using the product.

  • Extending product function

    Learn how to extend the product.

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

  • Troubleshooting and support

    There are a number of self-help information resources and tools to help you troubleshoot problems.

Ouncemake properties file elements

OuncemakeProperties, the root element of the Properties file, contains the elements that are listed in this topic.

Required elements:

  • Compiler
  • Linker
  • Make

Optional elements:

  • MakeOptions
  • Options
  • GlobalProjectOptions
  • FileOptions
  • Executable
  • MountRoot
  • 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.
  • Share: Email
  • Twitter
  • Disclaimer
  • Privacy
  • Terms of use
  • Cookie Preferences