Top-level directory open-wonka

This directory contains the global Jamrules for Wonka, a Jamfile, and the following text files:

README
General information about Wonka.
README.build
How to build Wonka from the sources.
README.install
How to install a pre-compiled binary.
README.licensing
Important licensing information.
COPYRIGHT
Yet more important licensing information.
but no source files. It has the following subdirectories:
Configuration
Steerfiles for the Wonka build process.
awt
Contains AWT implementations.
build-<cpu>-<hostos>
Used at build time to hold output and generated files. The Wonka binary is produced in build-<cpu>-<hostos>/wonka.
class
Used to collect class files during Java compilation. (Created on demand).
compiler
Contains runtime compiler implementations.
doc
Contains a makefile to build all LaTeX documentation, and templates used by the LaTeX documentation.
fs
Contains filesystem implementations.
jpda
Contains implementations of the Java Platform Debugging Architecture.
kernel
Contains implementations of the OSwald internal threading and memory management API: both the OSwald Reference Implementation and wrappers for various host operating systems.
network
Contains network stack implementations.
roadmap
Contains some text files outlining current ideas for development of Wonka.
sample
Contains sample applications.
tool
Contains tools (including the Mauve and VTE test suites) and scripts.
wonka
Contains the various non-optional components of the Virtual Machine and core class libraries.

When we say a directory "contains <foo> implementations", this means that the directory has two or more subdirectories, each of which contains one possible implementation of feature foo. Which implementation to use is decided at runtime by setting a Jam variable, e.g.

jam -sFS=native install
will cause subdirectory fs/native of fs to be used in the build. Often one of the subdirectories is called none, and provides a null implementation (no AWT, no runtime compiler, no filesystem ...).