Ounce/Make command syntax and make options

Ounce/Make supports multiple options that can change the way it behaves when it runs.

You can set these options in the Properties file (see Ounce/Make properties file for more details), or include them on the command line. If you set the options in the Properties file, it is not necessary to specify them on the command line every time you run Ounce/Make.


Ounce/Make supports the following syntax:

ouncemake [options] [-- make_options]


A hyphen (-) must precede all options. You must specify options separately; you cannot concatenate them after a single hyphen. For example, the command:

ouncemake -sr

is not supported syntax, but you can run:

ouncemake -s -r
Note: Each option must be separated by a space.

When you run Ounce/Make, you can use the abbreviated option or the complete word.

The following table includes columns describing each option.

  • Option: Identifies the option that Ounce/Make will understand when invoked.
  • Default: If applicable, explains how Ounce/Make operates by default if you do not specify the option.
  • Description: Ounce/Make behavior when using this option.
Option Default when option not specified Description
-a <application_name>
Off When specified, Ounce/Make creates an application file named <application_name>.paf that contains all projects created by Ounce/Make. The file is created in the directory in which ouncemake ran.
Off Perform the build while gathering the make options.

This option is incompatible with Cygwin.

Non-recursive Ounce/Make recursively follows all calls to other makefiles. For example, if a makefile exists at the root of a source code tree to call all of the makefiles in the subdirectories, then invoking ouncemake -r in the directory containing the root makefile causes Ounce/Make to follow the calls to the subdirectory makefiles.
Non-recursive Ounce/Make does not recursively follow calls to other makefiles.
Multiple-project mode Single-project mode. When in single-project mode, Ounce/Make generates only a single project file in the directory from which it is invoked.

If not specified, Ounce/Make is in multiple-project mode.

Multiple-project mode Multiple-project mode. In this mode, Ounce/Make generates an AppScan® Source project file in each directory for every makefile that it encounters.
Non-verbose mode Non-verbose mode. Ounce/Make only outputs its own output messages. Ounce/Make suppresses output from the make.
Verbose mode Verbose mode. Ounce/Make outputs the make's output, as well as its own, to standard output.
1 (off) 1 through 10. 10 provides the most logging.
-c <clean_command>
-clean <clean_command>
Off When specified, Ounce/Make interprets <clean_command> as a command, and executes it. <clean_command> should be the command that the user would normally execute to clean. For example, make clean is a common command for executing a clean. Note that you must enclose the command in quotation marks.

Since Ounce/Make requires a clean before running, if you do not specify this option, a prompt appears asking if you want to continue.

Off Tell Ounce/Make not to run clean and do not display a prompt reminding that a clean is not going to be run.
-p <properties_file>
n/a Allows users to specify a properties file for Ounce/Make to use. <properties_file> must be an absolute path to the properties file that Ounce/Make should use.
n/a Help for Ounce/Make options.