lispdoc - results for compile-file

(compile-file input-file &key
 (output-file (cfp-output-file-default input-file))
 ((verbose *compile-verbose*) *compile-verbose*)
 ((print *compile-print*) *compile-print*) (external-format default)
 (trace-file nil) ((block-compile *block-compile-arg*) nil)
 (emit-cfasl *emit-cfasl*))
Function: Compile INPUT-FILE, producing a corresponding fasl file and returning its filename. :PRINT If true, a message per non-macroexpanded top level form is printed to *STANDARD-OUTPUT*. Top level forms that whose subforms are processed as top level forms (eg. EVAL-WHEN, MACROLET, PROGN) receive no such message, but their subforms do. As an extension to ANSI, if :PRINT is :top-level-forms, a message per top level form after macroexpansion is printed to *STANDARD-OUTPUT*. For example, compiling an IN-PACKAGE form will result in a message about a top level SETQ in addition to the message about the IN-PACKAGE form' itself. Both forms of reporting obey the SB-EXT:*COMPILER-PRINT-VARIABLE-ALIST*. :BLOCK-COMPILE Though COMPILE-FILE accepts an additional :BLOCK-COMPILE argument, it is not currently supported. (non-standard) :TRACE-FILE If given, internal data structures are dumped to the specified file, or if a value of T is given, to a file of *.trace type derived from the input file name. (non-standard) :EMIT-CFASL (Experimental). If true, outputs the toplevel compile-time effects of this file into a separate .cfasl file.
Example:
(defun compile-paip-file (name)
  (let ((path (paip-pathname name :lisp)))
    (load path)
    (compile-file path :output-file
                  (paip-pathname name :binary))))
Mentioned in:
CLtL2 - 11.7. Package System Functions and Variables
CLtL2 - 23.1.5.3. Using Logical Pathnames
CLtL2 - 23.1.5.5. Discussion of Logical Pathnames
CLtL2 - 23.4. Loading Files
CLtL2 - 25.1. The Compiler
CLtL2 - 25.1.1. Compiler Diagnostics
CLtL2 - 25.1.2. Compiled Functions
CLtL2 - 25.1.3. Compilation Environment
CLtL2 - 25.1.4. Similarity of Constants
CLtL2 - 5.3.3. Control of Time of Evaluation
CLtL2 - 6.3. Equality Predicates
CLtL2 - 7.1. Reference
CLtL2 - 8.4. Compiler Macros
HyperSpec - Function COMPILE-FILE
PCL - defining your own packages
PCL - delivering applications
PCL - eval when
PCL - foo special operators
PCL - macros
PCL - other special operators
PCL - package gotchas
PCL - packaging mechanics
PCL - saving your work
PCL - where to go next
Successful Lisp - chapter28
Successful Lisp - chapter31
(asdf:compile-file* input-file &rest keys &key output-file &allow-other-keys)
Undocumented
  
(compile-file-pathname input-file &key (output-file nil output-file-p)
 &allow-other-keys)
Function: Return a pathname describing what file COMPILE-FILE would write to given these arguments.
 Mentioned in:
CLtL2 - 23.1.5.3. Using Logical Pathnames
CLtL2 - 23.1.5.5. Discussion of Logical Pathnames
HyperSpec - Function COMPILE-FILE-PATHNAME
*compile-file-truename
 
 Mentioned in:
HyperSpec - Variable *COMPILE-FILE-PATHNAME*, *COMPILE-FILE-TRUENAME
*compile-file-pathname*
Variable: The defaulted pathname of the file currently being compiled, or NIL if not compiling.
 Mentioned in:
CLtL2 - 25.1. The Compiler
HyperSpec - Variable *COMPILE-FILE-PATHNAME*, *COMPILE-FILE-TRUENAME
*compile-file-truename*
Variable: The TRUENAME of the file currently being compiled, or NIL if not compiling.
 Mentioned in:
CLtL2 - 25.1. The Compiler
(asdf:compile-file-pathname* input-file &rest keys &key output-file
 &allow-other-keys)
Undocumented
  
asdf:*compile-file-failure-behaviour*
Variable: How should ASDF react if it encounters a failure (per the ANSI spec of COMPILE-FILE) when compiling a file? Valid values are :error, :warn, and :ignore. Note that ASDF ALWAYS raises an error if it fails to create an output file when compiling.
  
asdf:*compile-file-warnings-behaviour*
Variable: How should ASDF react if it encounters a warning when compiling a file? Valid values are :error, :warn, and :ignore.