Edit "build_herkforth_from_source

edit "build_herkforth_from_source_files" below.

Tips:

The first line is the page title.
Separate your paragraphs by at least one blank line.
To have a < in your text, enter <<.
To make a link put <l and <> around the wiki page name or web address. Like this: <lmy page<> NOTE: that's a lowercase ELL
To learn about other things you can do please see wiki syntax

Build herkforth from source files

"Source code in files. How quaint." -- Kent Beck

This page describes how to build herkforth from source files. see <lherkforth
bootstrapping<> for how <lherkforth<> recompiles itself.

<lherkforth<> is written in <lherkforth<>. This is very cool and everything,
but it's a bit tricky to get started.

kernel.s contains asm code for the source token interpreter, and just a few
words that were needed to get <lherkforth<> to start compiling itself.

The files blocks/* contain <lforth<> source in a text format very similar to
conventional forths. These files include code for the <lherkforth assembler<>,
many basic forth words and the <lherkforth interface<>. These files also
include code to completely compile a new version of the forth system and write
it to a new ELF file.

build.c parses blocks/* and creates a <lherkforth dictionary<>, a data section,
and a bunch of <lherkforth source tokens<>. (Exactly what the interpreter runs
on.) Then merges these into the binary compiled from kernel.s (kernel.s.o) to
create a nice big elf file (herkforth000).

When you run herkforth000, the forth kernel from kernel.s executes/compiles
the source we had in blocks/* (which was parsed and inserted into the
ELF by build.c.) The forth code compiles a new forth kernel and writes
it out to a new ELF file herkforth001 along with all the source code we have
in the current ELF file. Then it starts executing the new version just
as though you had executed herkforth001.

<lherkforth<>

Anti-Robot: Please enter your favorite four digit number here: