Keywords: dir

Next: 3 Build environment Up: HAFTA Release 1.0 Directory Previous: 1 Specific Directories Contents
Subsections

- 2.1 Platform-specific directories
- 2.2 Test directories

# 2 Other Directories

## 2.1 Platform-specific directories

If there is platform-specific code it should be placed in subdirectories to separate specific code from the generic code. (eg. place all neutrino-specific code in ./nto/, linux-specific in ./linux)

The platform-specific directory can be subdivided even further if there is a need to separate code on an architecture-by-architecture basis.

The subdivision beyond the platform level is not yet supported

## 2.2 Test directories

Each point in the tree can have a test directory. This will hold any code that is required to perform a test of the functionality contained in the code at that level. Directories that contain no code can still have a test directory, but the code contained in that directory will test some general functionality. This is because there is nothing specific to test at that level.

Examples:

overlord/test/
  will contain code to run tests that test the functionality of the overlord in general.

overlord/olrt/modules/test/
  will contain tests that tests something general about all modules, such as the nebuloid module framework itself.

overlord/olrt/modules/mod_something/test
  will contain tests that only tests the functionality of the module (in this case mod_something.)

Next: 3 Build environment Up: HAFTA Release 1.0 Directory Previous: 1 Specific Directories Contents