1.6 Compilation Manager Hook for Syntax Transformers

package: base

procedure
(register-external-file file
[ #:indirect? indirect?]) → void?
file : (and path? complete-path?)
indirect? : any/c = #f

Logs a message (see log-message) to the current logger at level 'info with the topic 'cm-accomplice. The message data is a file-dependency prefab structure type with two fields; the first field’s value is file and the second field’s value is #f (to indicate a non-module dependency). If the indirect? argument is true, the data is more specifically an instance of a file-dependency/options prefab structure type that is a subtype of file-dependency with one extra field: a hash table mapping 'indirect to #t.

A compilation manager implemented by compiler/cm looks for such messages to register an external dependency. In response, the compilation manager records (in a ".dep" file) the path as contributing to the implementation of the module currently being compiled. Afterward, if the registered file is modified, the compilation manager will know to recompile the module. An indirect dependency has no effect on recompilation, but it can signal to other tools, such as a package-dependency checker, that the dependency is indirect (and should not imply a direct package dependency).

The include macro, for example, calls this procedure with the path of an included file as it expands an include form.

procedure
(register-external-module file
[ #:indirect? indirect?]) → void?
file : (and path? complete-path?)
indirect? : any/c = #f

Like register-external-file, but logs a message with a file-dependency prefab structure type whose second field is #t.

A compilation manager implemented by compiler/cm recognizes the message to register a dependency on a module (which implies a dependency on all of that module’s dependencies, etc.).

1	raco make: Compiling Source to Bytecode
2	raco exe: Creating Stand-Alone Executables
3	raco distribute: Sharing Stand-Alone Executables
4	raco planet: Automatic Package Distribution
5	raco pkg: Package Management
6	raco setup: Installation Management
7	raco decompile: Decompiling Bytecode
8	raco demod: Demodularizing Programs
9	raco link: Library Collection Links
10	raco pack: Packing Library Collections
11	raco unpack: Unpacking Library Collections
12	raco ctool: Working with C Code
13	raco test: Run tests
14	raco docs: Documentation Search
15	raco expand: Macro Expansion
16	raco read: Reading and Pretty-Printing
17	raco scribble: Building Documentation
18	Adding a raco Command
19	Installation Configuration and Search Paths

1.1	Running raco make
1.2	Bytecode Files
1.3	Dependency Files
1.4	API for Making Bytecode
1.5	API for Parallel Builds
1.6	Compilation Manager Hook for Syntax Transformers
1.7	API for Simple Bytecode Creation
1.8	API for Bytecode Paths
1.9	Compiling to Raw Bytecode
1.10	API for Raw Compilation
1.11	API for Reading Compilation Dependencies