IDE Dialog Tab |  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version

## Project Manager Advanced Tab

The Advanced Tab of the Project Manager Dialog displays certain advanced options for the application associated with the project. The options and controls are:

- Deliver a Runtime Bundle: Specifies whether the runtime-bundle argument to generate-application should be specified true (checked) or not (unchecked). When that argument is true, a runtime-suitable bundle file (containing modules permitted in a runtime image but not loaded into the image as built) will be included in the distribution directory. See Including all desired modules in delivery.htm for more information. See also build-flags.
- Purify: Specifies whether to move strings and code vectors that would otherwise be in the generated .dxl image file into a separate .pll library file, which is sharable by multiple lisp applications. (Checking this box is equivalent to specifying the purify argument to generate-application true.) See also build-flags.
- Autoload warning: If checked, the autoload warning dialog will be displayed when a project build is complete. If unchecked, it will not be displayed. (Not displayed it facilitates batch processing.) See autoload-warning.
- Run With Console: whether the standalone application should have a console window whose read-eval-print loop is always active. See cg:run-with-console.
- For US Government Use: check this if the application will be supplied to the US Government or someone working for the US Government (and the application is in connection with that person's work). If this box is checked, the copyright notice will include language that protects the rights of software vendors (the application developer and Franz Inc.) when supplying the US Government. That is the only effect of selecting this option. Note that it is not necessary to select this option when supplying a government of any country other than the United States or supplying a state or local government in the United States. See also build-flags.
- Old Space: specifies the size of the initial oldspace in the application. The oldspace will grow automatically as needed but specifying a suitable value can improve garbage collection performance. See gc.htm for more information on oldspace size and garbage collection. See old-space-size.
- New Space: specifies the size of the initial newspace in the application. The newspace will grow automatically as needed but specifying a suitable value can improve garbage collection performance. See gc.htm for more information on newspace size and garbage collection. See new-space-size.
- Command Line Arguments: specifies default command line arguments (such as +c -foo) that will be passed to the generated executable automatically; see default-command-line-arguments.

  As described below, a project will prepend either `+cx` or `+c` to these options internally, and so it is generally not necessary to specify a `c` option explicitly here.

  The initial value for a new project includes the `+M` flag (to ensure that the standalone application fully exits when it attempts to exit with a non-zero exit code after an error), and also `+t` Console for Debugging (as a suggested title for the Console window, in case it were to be included with a delivered application). These flags are recommended for CG applications, though you may wish to add additional flags.

  In addition to the command line arguments specified explicitly in this widget, either the `+cx` or `+c` flag will be added internally by the project system. If Enable Debugging of Runtime Errors is selected on the Build tab, then `+cx` will be added to include the console window in the application; it will be hidden but may be exposed for debugging. If Enable Debugging of Runtime Errors has been unselected (as you would typically do before delivering an application), then `+c` is passed to exclude the console window entirely from the application; this will also suppress the console's tray icon.

  See Command line arguments and its subsections in startup.htm for a table of standard command-line options.

- Additional Build-Lisp-Image Arguments: specifies the values of any needed arguments to generate-application or build-lisp-image that are not covered by more specific project properties. The values entered here will form the plist that is the value of the additional-build-lisp-image-arguments property of the project. Text should be entered into this widget as this plist would print, except without the surrounding parentheses; for example:

      :read-init-files nil :c-heap-size #x400000

- Default Error Handler for Delivery: specifies the value of the default-error-handler-for-delivery property of the current project. The value should be the name of a function that accepts a single argument, which will be a condition object. This function will be called in the standalone application for any otherwise unhandled errors if the Enable Debugging of Runtime Errors option has been disabled on the Build tab for final delivery. It is a good idea to include a package qualifier on the function name when entering it here, and the qualifier will continue to be displayed here in the future.

See the general description of the Project Manager Dialog for details of the toolbar buttons.

Copyright (c) 1998-2022, Franz Inc. Lafayette, CA., USA. All rights reserved.
This page was not revised from the 10.0 page.
Created 2019.8.20.

|  | ToC | DocOverview | CGDoc | RelNotes | FAQ | Index | PermutedIndex
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version