"BuildProcessor.1.xml" Ozer Ozkaraoglu Builds the code of a given manifest along with all other manifests it is directly/indirectly referring to. softTools_buildScript_diagrams1_raster.jpg softTools_buildScript_diagrams2_raster.jpg contains information about type of the operation which will be performed The requested task is given by this input. is the data (content) coming from the foundry files Manifest and project files are read to gather the necessary information for build, while some other files (e.g. code files) are accessed during build process.

contains information about the status of the operation The user notification messages about the current status of the operation, along with the possible warning messages of the compiler.

contains the text about nature of the error An error message is created when an error occurs.

contains the physical location of a file The file system is sent filename to begin writing an output of build operation.

is the compiled data coming from the build script All data is created at saveDir, which was given by Build Script Command Line Handler

building system manifest Builds an executable file for a system type manifest building program manifest, Req: (3.1.24.3) Builds an executable file for a program type manifest, and builds the dynamic link library compilation of all manifests it directly/indirectly refers to. These dll files may not be compiled if they already exist. building module manifest, Req: (3.1.24.1) Builds an executable file for the test driver and dynamic link library of a module type manifest. The dll files of all (in)directly referred files are also created. Again, they may not be created if they already exist. saveDir - all necessary files must already be extracted into this directory, Req: (3.1.24.2) Checks the validity of the path given by saveDir, and halts and passes an appropriate errorMessage if the directory is invalid. The program also halts whenever a necessary file is not found in this directory. All operations are made in this directory, and thus all MODIFICATIONS are made on files in this directory only. invalid manifestName given It should halt and return an appropriate errorMessage invalid buildConfig given It should halt and return an appropriate errorMessage compiler error errorMessage holding the message of compiler is passed to the standard output name conflict A manifest indirectly using two different versions of the same class is built.It sends statusMessage to standard output, which is the warning message of the compiler. The program, however, does not halt.