Release Notes for BCB programs

The following are precautions for release of BCB programs on the network. The information comes from the network.

Generally, we release the program as follows:

In prject-> options-> compiler, click release,
Remove the builder with runtime packages option from prject-> options-> packages.
Remove the use dynamic RTL option from prject-> options-> linker.
Then rebuild

It is best to use UPX to compress the EXE file.
Effect: Green, applicable to general programs, without Borland Environment

To reduce the size of the final program and better share the dynamic link library, I release the program like this.

In prject-> options-> compiler, click release,
In prject-> options-> packages, check the builder with runtime packages option.
Check the use dynamic RTL option in prject-> options-> linker.
Then rebuild

It is best to use UPX to compress the EXE file.
Effect: the database needs to be linked, but the generated program is small, which facilitates network transmission and provides users with upgrading programs.
======================================
A basic visualization program has the following files:
Vcl60.bpl Borland package Library
Rtl60.bpl Borland package Library
Borlndmm. dll Borland Memory Manager
Cc3260mt. dll run time Library

In addition, pagecontrol, bitbutton, and so on are only required.
Well, some people once said that Borland's things generate a large program, because Microsoft has put many of its own linked libraries in windows, if we put these link libraries of Borland into system32, the Borland program can be as small as it is.