► |  | mzc: PLT Compilation and Packaging

1 | Running mzc
2 | Compiling Modified Modules to Bytecode
3 | Creating and Distributing Stand-Alone Executables
4 | Packaging Library Collections
5 | Compiling and Linking C Extensions
6 | Embedding Scheme Modules via C
7 | Decompiling Bytecode
8 | Compiling to Raw Bytecode
9 | Compiling to Native Code via C
10 | Scheme API for Compilation
| Index

▼ | 3 | Creating and Distributing Stand-Alone Executables

3.1 | Stand-Alone Executables from Scheme Code
3.2 | Distributing Stand-Alone Executables
3.3 | Installation-Specific Launchers for Scheme Code

top ← prev up next →

### 3`` Creating and Distributing Stand-Alone Executables

Whether bytecode or native code, the compiled code produced by mzc relies on PLT Scheme executables to provide run-time support to the compiled code. However, mzc can also package code together with its run-time support to form a complete executable, and then the executable can be packaged into a distribution that works on other machines.

3.1 Stand-Alone Executables from Scheme Code
3.1.1 Scheme API for Creating Executables
3.1.1.1 Executable Creation Signature
3.1.1.2 Executable Creation Unit
3.2 Distributing Stand-Alone Executables
3.2.1 Scheme API for Distributing Executables
3.2.2 Scheme API for Bundling Distributions
3.3 Installation-Specific Launchers for Scheme Code
3.3.1 Creating Launchers
3.3.2 Launcher Path and Platform Conventions
3.3.3 Launcher Configuration
3.3.4 Launcher Creation Signature
3.3.5 Launcher Creation Unit

top ← prev up next →