Knowledgebase: HierCube VCL
How to install the components of HierCube VCL manually
Posted by Ivan Pashkov on 23 May 2013 12:05 PM

Most often there is no need to install the HierCube components manually because the installer does it automatically. However sometimes there may be a reason to do so. For example, you need to recompile the packages with different parameters/directives and reinstall them into the IDE. This article explains the structure of the packages in HierCube library and how to install them into the IDE without the installer.

Structure of the packages

When you install the HierCube distributive into your system you have several folders under the root HierCube installation folder. Every installation has at least the folder named LIB that contains all necessary files to install all components into the IDE. Most important files are the compiled packages (.bpl and .dcp files). Also there are recourse and .dfm files that you also need for installation. There are several packages that contain different units of HierCube. The packages firmly divided for run-time packages and design-time packages. That means there is not a single package that is run-time and design-time at the same time. This is done to provide the run-time part of the code that may be compiled under WIN64 platform. Eight packages contain all HierCube components and helper classes:

Run-time packages:

xhCntrlsRtl170.bpl – The run-time part of all the helper components used in HierCube
xhHierCubeRtl170.bpl – The run-time part of the main HierCube components
xhChartRtl170.bpl – The run-time part of HierCubeChart component
xhExportRtl170.bpl – The run-time part of all the export components

Design-time packages:

xhCntrlsDsgn170.bpl - Helper Unicode components used in HierCube
xhHierCubeDsgn170.bpl - HierCube and HierCubeGrid components
xhChartDsgn170.bpl - HierCubeChart component
xhExportDsgn170.bpl - Export components like HierCubeGridExportToHTML

As you can see the run-time packages have the suffix "Rtl" while design-time packages marked with "Dsgn" suffix. And of course, the suffix "170" may be any other valid package identifier depending on the IDE you use. For example, RAD Studio 2007 has the packages with suffix "110", RAD Studio 2009 – "120" and so on.

Removing the previous packages from the computer

In spite of the fact that the uninstaller in most cases will remove all packages for you, there might be a chance that some garbage packages remain on your computer's disks. (For example if a package is used at the moment of uninstallation it will not be removed). So, before you install the new packages into the system you need to remove the old ones to avoid possible conflicts. To do so you have to search your system drive and the one that RAD Studio installed to for all compiled packages of HierCube (.bpl and .dcp files) and delete them.

For example, the installer puts all .bpl and .dcp files into the following directory by default: "C:\Program Files\RadarSoft\HierCube\DXE3\lib". On the other hand, if you install the packages manually the .bpl and .dcp files by default are located in "C:\Users\Public\Documents\RAD Studio\10.0\Bpl" and "C:\Users\Public\Documents\RAD Studio\10.0\Dcp" as defined in the IDE path. So the best way is to find all occurrences of xh*.bpl and xh*.dcp on the whole computer and delete them all.

Installing the packages without the source code

No matter, whether you have the evaluation license of HierCube or the developer license with source code, – you always have the compiled packages (.bpl files) that you may install into the IDE. However you must first copy all .bpl files into the folder in the system Path variable. The installer writes the folder where it puts the .bpl files (for example, "C:\Program Files\RadarSoft\HierCube\DXE3\lib") into the Path variable so in this case there is no need to copy the files anywhere else. Once you copied all the BPLs run Component > Install packages... menu command and click Add… button. After that choose the design-time packages (four packages marked with the "Dsgn" suffix) and click Open to install them into the IDE. That is it. Now you should be able to use the components in the IDE.

Installing the packages with the source code

If you have the distributive with the source code then you can use another method to install the components into the IDE. With the source code the packages are shipped not as .bpl and .dcp files but as .bpk and .res files.

To install them into the IDE you must first open all run-time packages (the ones with "Rtl" suffix) and Compile them. Be sure to compile first the package xhCntrlsRtl and the second xhHierCubeRtl. This is important! The other packages may be compiled in any order. Compiling will force the IDE to put the resulting .bpl and .dcp files into corresponding folders written in "BPL (Package) output directory" and "DCP output directory" fields, so that later IDE may find them.

After that you must open all design-time packages (the ones with "Dsgn" suffix) and Install them. You can install the design-time packages in any order as they do not depend on each other. Now you should be able to use the components in the IDE.

(4 vote(s))
This article was helpful
This article was not helpful

Help Desk Software by Kayako Resolve