Copying Buildspecs
Running the RCB GUI across a network can be slow. Also, certain combinations of Java Virtual Machine implementations and display environments do not seam together well, sometimes yielding bugs in the GUI rendering process.
RCB allows a buildspec file to be created on one RCB installation and then executed on another. This allows you to work around the GUI rendering problems.
You can copy a local build or an export build. An example of each is listed below. For the purposes of the example, two definitions must be defined:
Local Installation: The on site installation of RCB, preferably displayed on the same machine it is being run on.
Remote Installation: The installation of RCB in which builds need to be executed.
Copying Local Buildspecs
This example assumes that you are working on a Windows platform.
Install RCB and SourcePro components in both the local and remote installations. Both installations must have the same products installed.Create a new buildspec in the local RCB installation.On the Select Buildspace screen, use the local buildspace value that is appropriate for the local installation.On the Select Operating System screen, specify the operating system that is appropriate for the remote environment where the buildspec will be executed.On the Select Compiler screen, specify the compiler that is appropriate for the remote environment where the buildspec will be executed.On the Select Naming Convention screen, add a user-tag to help identify the buildspec. This makes it easier to handle the buildspec files directly.On the Build Queue screen, create all required buildspecs, then exit RCB. These buildspecs will automatically be added to the Build Queue screen. Do not launch the builds locally.Copy the newly created buildspec files (recognized by the .bsf extension) from <buildspace_of_local_installation>\records\specs\ to a location accessible by the remote system.Execute the copied buildspec files on the remote machine via a command line build.For this copy attempt to work, the buildspace value in the buildspec must be appropriate for the machine it will build on. To make the buildspace value appropriate, it must be changed or overridden. Rogue Wave recommends using the existing RCB command line option (-S) to override the buildspace value at build time:
rcb build -b <desired_buildspec> -S <buildspace_of_remote_installation>
NOTE: Note that this does not replace the buildspace value in the buildspec file itself. For more help on the override options available in RCB, type:
rcb build -help
rcb build -help
Copying Export Buildspecs
This example assumes that you are working on a Windows platform.
Install RCB and SourcePro components in both the local and remote installations. Both installations must have the same products installed.Create a new buildspec in the local RCB installation.On the Select Buildspace screen, use the local buildspace value that is appropriate for the local installation.On the Select Operating System screen, specify the operating system that is appropriate for the remote environment where the buildspec will be executed.On the Select Compiler screen, specify the compiler that is appropriate for the remote environment where the buildspec will be executed.On the Select Naming Convention screen, add a user-tag to help identify the buildspec. This makes it easier to handle the buildspec files directly.On the Build Queue screen, create all required buildspecs, then exit RCB. These buildspecs will automatically be added to the Build Queue screen. Do not launch the builds locally.Copy the newly created buildspec files (recognized by the .bsf extension) from <export_buildspace_of_local_installation>\records\specs\ to a location accessible by the remote system.Execute the copied buildspec files on the remote machine via a command line build.For this copy attempt to work, the buildspace value in the buildspec must be appropriate for the machine it will build on. To make the buildspace value appropriate, it must be changed or overridden. Rogue Wave recommends using the existing RCB command line option (-S) and (-E) to override the buildspace value at build time:
rcb build -b <desired_spec> -S <local_buildspace_of_remote_installation>
-E <export_buildspace_of_remote_installation>
Note that this does not replace the buildspace value in the buildspec file itself. For more help on the override options available in RCB, type:
rcb build -help
NOTE: When transferring export buildspecs, ensure that all specs transferred into a given export_buildspace_of_remote_installation have consistent settings for the “which files to copy” setting (headers vs. headers and source).
