This section provides several examples on how to use RKH, designed to experiment with RKH immediately. The simplicity of the code and state diagrams means it also serves as a good starter project for people who are not yet familiar with RKH. Also, this examples are demostration projects considered cross-platform, because of they are able to function on more than one computer architecture or operating system. The code of demos are located in the <rkh>/demo/cross/ directory, where <rkh> stands for the installation directory chosed to install the accompanying software. Each example contains the platform-independent source code and a build/ directory. The structure of the build branch closely mirrors the structure of the source/portable/ directory, which contains platform-specific header files and libraries to be used by RKH applications.
- (1) Reactive applications. The user code, which defines the active object, state machines, events, and the RKH configurations.
- (2) RKH framework. Platform-neutral code.
- (3) Platform abstraction layer, which encapsulates all the platform-specific code (processor, compiler, and operating system) and cleanly separates it from the platform-neutral code, (1) and (2) layers.
- (4) Board support package (BSP). Platform-dependent files, which implements RKH support on each platform defined by the (3) layer.
- (5) RKH port. Implements all the platform-specific code, which is defined by processor, hardware, compiler, and operating system in use.
- (6) Target hardware.
RKH cross-platform examples:
