-
Notifications
You must be signed in to change notification settings - Fork 113
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Document the metacompiling build process.
- Loading branch information
1 parent
6fefa7d
commit 42a965c
Showing
1 changed file
with
22 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,22 @@ | ||
This describes how lbForth is normally built. | ||
|
||
- To build a target, load its build.fth file. Every target should | ||
have one. | ||
|
||
- build.fth sets up some information about the target, and loads the | ||
generic compile.fth. | ||
|
||
- compile.fth loads the generic metacompiler framework. | ||
|
||
- The generic metacompiler loads a library for accessing a target image. | ||
|
||
- And creates vocabularies for metacompiling words. | ||
|
||
- compile.fth proceeds to add metacompiling words that target lbForth. | ||
|
||
- And a target assembler. | ||
|
||
- It then loads kernel.fth and cold.fth to build a target image. | ||
|
||
- Finally, forward references are resolved, and the image is saved to | ||
disk. |