LispWorks Delivery User Guide > 7 Delivery on Microsoft Windows


7.2 Application Manifests

LispWorks for Windows is supplied with an embedded application manifest. This default manifest tells the Operating System:

You can change the manifest in your delivered image by passing the keyword argument :manifest-file to deliver . The value must be the name of a file that is a legal application manifest, which is is used as the manifest. The manifest must contain at least the "dependency" element for Microsoft.VC80.CRT (without it, your application will fail to start with error messages "Failed to find msvcr80.dll" or "The application configuration is incorrect"). If the manifest does not contain the "dependency" element for Microsoft.Windows.common-controls your application will use Common Controls 5, and therefore will not be a "Themed" application.

The value of :manifest-file can also be the special value :no-common-controls-6 , in which case a default manifest without the element for Common Controls is used.

The default manifests that LispWorks uses are provided by way of documentation in the lib/6-0-0-0/config directory. If desired, you can base your application manifests as supplied via :manifest-file on these files:

The default manifests used by LispWorks


32-bit LispWorks

64-bit LispWorks

With Common Controls 6



Without Common Controls 6



Note: the above only applies when LispWorks is an executable. If LispWorks is a DLL, then it will be themed if the executable that loads it contains the Common Controls 6 manifest

LispWorks Delivery User Guide - 22 Dec 2009