Q 3.8-1) I get an error when I try to build an image with
excl:build-lisp-image (and also with excl:generate-application) but the build process
simply quits. How can I debug this error?
Q 3.8-4) I notice that when I run generate-application, a license file is
placed in the distribution directory. Is that license file tied to the image file?
Q 3.8-1) I get an error when I try to build an image with excl:build-lisp-image (and also with excl:generate-application) but the build process simply quits. How can I debug this error?
A 3-8.1) Since generate-application calls build-lisp-image, the same answer applies to both functions.
See section Debugging an image build problem or failure in building-images.htm.
Q 3.8-4) I notice that when I run generate-application, a license file is placed in the distribution directory. Is that license file tied to the image file?
A 3.8-4) There is a license file created when generate-application is called. It is named <application-name>.lic and is placed in the distribution directory. It must be there to run the application and it is tied to the application image (dxl) file: it only works with that image file and that image file only works when the license file is present. If you have to update the image file (for example, to add new features to the application or to fix bugs), be sure to create the new image using generate-application (which will, of course, create a whole directory of files including the image and a new license file) and be sure to send at least both the image and the license file to the application users. (The more typical thing to do is to send the whole directory.)
Next FAQ topic: 3.9 Heap placement issues
Previous FAQ topic: 3.7 The stepper
ɠCopyright 1999, 2002, 2004 Franz Inc., Berkeley, CA. All rights
reserved.
$Revision: 1.2 $