Re: RE: RE: Package build is going slow
Here is the text from an old document. I cannot even find it on the KG anymore or I would refer you to the doc number. I am hoping that if you understand the process in detail, you will be able to understand the performance issues.
Full Client Build
======================
Depending where the package build is run from, R9621 is run on the Workstation or the Deployment Server.
The following takes place on the Deployment Server and is graphically represented in Section II.
The packagename directory is created.
(\\deploymentserver\b7331\pathcode\packages\packagename)
The packagename.inf file is created.
(\\deploymentserver\b7331\package_inf\packagename.inf)
The bin32 and res directories are copied from the check-in directory to the packagename directory.
From: (\\deploymentserver\b7331\pathcode\bin32)
To: (\\deploymentserver\b7331\pathcode\packages\packagename\bin32)
From: (\\deploymentserver\b7331\pathcode\res)
To: (\\deploymentserver\b7331\pathcode\packages\packagename\res)
The source, include, make, and work directories are copied from the check-in directory to the packagename directory. Lib32 and obj directories are just created, but no files copied in.
From: (\\deploymentserver\b7331\pathcode\source)
To: (\\deploymentserver\b7331\pathcode\packages\packagename\source)
From: (\\deploymentserver\b7331\pathcode\include)
To: (\\deploymentserver\b7331\pathcode\packages\packagename\include)
.
.
.
(The directories described in 3 are only copied if you do not check mark - Build Business Functions)
(4 a and b happen simultaneously)
a. Spec files and indexes are generated – RDB records are used to generate .ddb Spec files and
.xdb index files are generated off the DDB files.
The files generated are placed in (\\deploymentserver \b7331\pathcode\packages\packagename\spec)
Examples: fdaspec.ddb, fdaspec.xdb
gbrspec.ddb, gbrspec.xdb
rdatext.ddb, rdatext.xdb
b. Busbuild is run from workstation or deployment server, depending on where R9621 was run
from.
NER is generated (n*.c, n*.h and f*.c, f*.hxx)
The n*.c and f*.c files are placed in
(\\deploymentserver b7331\pathcode\packages\packagename\source)
The n*.h and f*.hxx files are placed in
(\\deploymentserver \b7331\pathcode\packages\packagename\include)
Make files are generated.
The location where the make files are placed, depends on where the R9621 was run from.
If R9621 is run from the deployment server:
(\\deploymentserver\b7331\pathcode\obj)
If R9621 is run from the a client workstation:
(rootdrive:\b7\pathcode\obj)
C code is compiled into *.obj files.
(\\deploymentserver\b7331\pathcode\packages\packagename\obj)
Linking of obj files into libraries
(\\deploymentserver\b7331\pathcode\packages\packagename\lib32)
Creation of .dlls from libraries
(\\deploymentserver\b7331\pathcode\packages\packagename\bin32)
9. NER is copied to check-in location
(n*.c and f*.c files)
From: (\\deploymentserver\b7331\pathcode\ packages\packagename\source)
To: (\\deploymentserver\b7331\pathcode\source)
(n*.h and f*.hxx files)
From: (\\deploymentserver\b7331\pathcode\ packages\packagename\include)
To: (\\deploymentserver\b7331\pathcode\include)
10. Package is compressed (**if options are checked – helps, foundation and data are also compressed)
(\\deploymentserver\b7331\pathcode\ packages\packagename\*.cab)
11. The bin32, lib32 and obj directories are copied to check-in location.
From: (\\deploymentserver\b7331\pathcode\ packages\packagename\bin32)
To: (\\deploymentserver\b7331\pathcode\bin32)
From: (\\deploymentserver\b7331\pathcode\ packages\packagename\lib32)
To: (\\deploymentserver\b7331\pathcode\lib32)
From: (\\deploymentserver\b7331\pathcode\ packages\packagename\obj)
To: (\\deploymentserver\b7331\pathcode\obj)