Paths

The configure command creates the Paths file in build_dir. For each source component, the Paths file defines two subdirectories, one located in source_dir and one in build_dir.

The ChorusOS source code environment will not allow modification of any file outside your work directory. Consequently, regardless of where the source directories of a component are kept, they will be compiled in that component's subdirectory in build_dir. An example Paths file for UltraSPARC is shown in

Example 3-1 A Paths File

BUILD_DIR=build_dir
NUCLEUS=/install_dir/chorus-usparc/kernel
NUCLEUS_DIR=/install_dir/chorus-usparc/kernel
BSP=/source_dir/nucleus/bsp/usparc/cpxxxx
BSP_DIR=build_dir/build-BSP
DRV=/source_dir/nucleus/bsp
DRV_DIR=build_dir/build-DRV
OS=/install_dir/chorus-usparc/os
OS_DIR=/install_dir/chorus-usparc/os
FLITE=/install_dir/chorus-usparc/opt/Flite
FLITE_DIR=/install_dir/chorus-usparc/opt/Flite
DEVTOOLS=/install_dir/chorus-usparc/tools
DEVTOOLS_DIR=/install_dir/chorus-usparc/tools
CDS=/install_dir/chorus-usparc/tools
CDS_DIR=/install_dir/chorus-usparc/tools
CDS60=/install_dir/chorus-usparc/tools
CDS60_DIR=/install_dir/chorus-usparc/tools
CHSERVER=/install_dir/chorus-usparc/tools
CHSERVER_DIR=/install_dir/chorus-usparc/tools
CHTOOLS=/install_dir/chorus-usparc/tools
CHTOOLS_DIR=/install_dir/chorus-usparc/tools
EWS=/install_dir/chorus-usparc/tools
EWS_DIR=/install_dir/chorus-usparc/tools