What files are required for the CB generated program

For example, c++builder5.0, the other versions are similar, where the default setting for c++builder1.0 is to run independently.

1. In the BCB IDE environment, press the Project menu and go to the linker page, there is a use dynamic RTL option in the linking item, do not select it. This relates to whether the following two files are required to compile the generated EXE: Borlndmm.dll and Cc3250mt.dll. If use dynamic RTL is selected, the program will search for the two files in the directory of the program EXE and the Windows system directory, and mount it. If it is not selected, the two files will not be required. Different versions of the C++builder, May cc3250mt.dll name is different, such as cb3.0 for Cp3240mt.dll.

2. Runtime Package: Press the Project menu and go to the Packages page, build the With runtime packages option in the runtime packages entry, if you do not select it, BCB will statically link all used libraries at compile time. The contents of the edit box under it have no effect. This means that the program does not require a run-time package. If you select it, you can add or remove packages that run in a fashion in the edit box under Options, if the program uses a component in a package, if the package is not in the edit box package list, even if the build with runtime Packages is selected, the program does not need this runtime package when it is run, and further, if the Package list edit box is selected with the runtime packages but the packages are empty, the result is not selected Buider runtime Packages is the same. The settings are the same for Third-party components, including components that you compile.

The above two settings change and you can build project again.

If we do not need to generate stand-alone EXE, but rather to know exactly what packages are needed to run after my program is distributed (perhaps build with runtime packages checked and the following edit box is included in all of the runtime packages), you can refer to the following instructions:

Component Runtime Package Other requirements

The tdatabase,ttable of the data access page, and so on, accesses the database control through BDE VCLBDE50.BPL they are based on BDE connection database, need the computer to install BDE, and the corresponding SQL database client program (DBF and so on local database need not)

ADO Page Tadocommand control based on ADO connection database: VCLADO50.BPL requires the computer to install ADO to run the Mdac_typ.exe on the BCB installation disk. This page control is available in cb5.0 version.

Tibeventalerter and other controls under the Samples page VCLSMP50.BPL

Data Controls page Tdbedit and other controls VCLDB50.BPL

Midas Page TClientDataSet and other controls VCLMID50.BPL need Midas.dll (lower version is Dbclient.dll)

TButton and other controls for standart/dialogs pages VCL50.BPL

Components such as tibquery for InterBase component pages VCLIB50.BPL need to install InterBase client to access InterBase server.

Quickreport Component VCLX50.BPL&QRPT50.BPL

............

It is best to use the Install Shield Express for C++builder to make the installation disk, as long as the components used in the Setup program, ISX can automatically add the required BPL to the installation works, save time and effort and error-prone. ISX also provides BDE installation features.

There is also a very simple way to try out what packages are needed for a program: copy BCB design-generated programs that require a run-time package in a "blank" windows that is not installed BCB, and all runtime packages (BPL of BCB *.BPL and Third-party components in Windows directory) Copy to the program directory, and then run the program, one by one delete BPL, can not be deleted BPL is the program is required to run.

3. In any case, if the program uses a control that connects to the database (DataAccess page) through BDE, then you need to install BDE under windows at run time. If you use Third-party components, you should also be aware that these components require other DLLs and other files.