include-flags

Arguments: project

Returns a list of keyword symbols indicating certain arguments that will be passed to either generate-application or build-lisp-image when the File | Build Project Exe or File | Build Project Distribution command is used to generate a standalone application for the specified project. The list may contain any combination of the symbols (:compiler :local-name-info :top-level). All three symbols are included by default.

The setf of this function may be called to establish the set of flags programmatically, but typically these values are set interactively on the Advanced tab of the Project Manager dialog instead, in the Build Includes list widget. Most of the options in this list widget map to the runtime-modules property of the project, but the three with names similar to these three keywords correspond to this property.

When :compiler is included in the list and the runtime-build-option property of the project is :dynamic or :partners (rather than :standard, which is the default), then the :discard-compiler argument to generate-application is passed as nil to include the compiler in the standalone application. (The appropriate Allegro license is required for this.) When :compiler is excluded from the list or when the runtime-build-option property of the project is :standard, the :discard-compiler argument is passed as t.

When :local-name-info is included, the :discard-local-name-info argument to generate-application or build-lisp-image will be nil, and otherwise will be t. When :top-level is included, the :include-tpl argument will be t, and otherwise will be nil.

Copyright (c) 1998-2002, Franz Inc. Oakland, CA., USA. All rights reserved.
Documentation for Allegro CL version 6.2. This page has had significant revisions compared to the 6.1 page.
Created 2002.2.26.