1.1 Implementation of the project system integration release
The final product of the project, that is, the target system is co-assembled by each component and reference third-party development kit, which can be considered that its source is the source code of each component, and must be included in the configuration management only to build scripts and specifically for acceptance tests.
In response to the above features, the source code structure organization of the system is shown in the following figure below:
table of Contents
Description
Note
build
Build a script
Incorrecting configuration management
TEST / EXAMPLE
Verify that the system successfully compiles, installs test or sample code
Incorrect in configuring management if test code for other components can be written or modified
Include
The system is a public header file (ie interface) directory issued by the development package.
It is usually automatically copied from the construction script in the installation step.
Lib
System as a static library issued by the development kit
It is usually automatically copied from the construction script in the installation step.
DOC
User reference document
It is usually automatically copied from the construction script in the installation step.
bin
Executable file and dynamic library
It is usually automatically copied from the construction script in the installation step.
Build a script to perform steps:
First, initialization (-init) is performed, ready to compile the configuration; Clean, get clean work space; complete build preparation (-PREP), create some temporary directory and target directory (lib); open the installation process ( INSTALL), automatically copy the public header file (ie, interface) to include from other components and third-party development kits, and copies the user reference document to be published to the DOC, copy the static library to LIB, will be The published executable and dynamic library copy to bin, and finally set an environment variable to the current system running an image root directory; perform test preparation (-TestPrep), from other component organization related test code, copy to test / example under. Test Built, generate test execution files; execute test (TEST), verify that the system is successfully installed, and the components that use it for secondary development can be compiled normally, and can be tested.
1.2 Batch Build Steps
In order to facilitate construction, all buildings issued by third-party development kits, project sub-components, and system integration are typically performed by batch order. The / PCHL_SYSTEM / INTEGRATION / Build directory has a batch command script all.bat for automatically performing the above process.
The way the batch is mainly implemented by the sub-Ant project execution function provided by Ant, see the relevant batch XML file.
Third-party development kits libraries batch script placed under / libraries / libs_bundle / batch-build, eventually generated 3D_Party.lib for all third-party development libraries (last call / librat / libs_bundle / build) The next build script is generated and placed under / libraries / libs_bundle / lib).
The infrastructure infrastructure batch process is similar to libraries that also generate infrastructures.lib (placed under / infrastructure / infrS_bundle / lib).
System Integration Publishing In / PCHL_SYSTEM / INTEGRATION / Build Directory has a batch script BatchBuild.xml, the build script of all components will be automatically called, and the integrated release build script will generate the publishing image of the system in the final call.
