| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version |
Arguments: &key include-new-efs files bundle tdir bundle-prog bli-tf
Although this function can be called at any time, it is generally only needed if a patch is downloaded from Franz Inc., which when built into the Lisp, displays a message at startup time advising the user to call this function.
If a user defines a new external-format which s/he wants to be autoloadable in a runtime application, the definition should be made in a file named code/ef-[name].fasl (where code/ is a subdirectory of the Allegro CL directory). When this function is called, a copy of the external-format definition file will be put into the bundle and runtime bundle. Note that only files named code/ef-*.fasl are placed into the bundle by this function.
This function updates the bundle file (returned by bundle-pathname) and also the runtime bundle file runtime.bu (if there is one). After the update, all module fasl files downloaded to the code/ subdirectory of the Allegro Directory will be included in the bundle. External format definitions not in the bundle will also be included.
Note that updating the bundle can take an appreciable amount of time.
The arguments are all keyword arguments. It is recommended that update-bundle-files be run without arguments (that is, the defaults be accepted in all cases). The arguments are:
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.
| Allegro CL version 10.1 Unrevised from 10.0 to 10.1. 10.0 version |