Deploying Packages
Go Up to Working with Packages and Components Index
You deploy packages much like you deploy other applications. The files you distribute with a deployed package may vary. The bpl and any packages or dlls required by the bpl must be distributed.
Files deployed with a package
| File | Description |
|---|---|
|
ComponentName.h |
Allows end users access to the class interfaces. |
|
ComponentName.cpp |
Allows end users access to the component source. |
|
.bpi, .obj, and .lib |
Allows end users to link applications. |
For general deployment information, refer to Deploying Applications.
Deploying applications that use packages
When distributing an application that uses runtime packages, make sure that your users have the application's .exe file, as well as all the library (.bpl or .dll) files that the application calls. If the library files are in a directory different from the .exe file, they must be accessible through the user's Path. You may want to follow the convention of putting library files in the Windows\System directory. If you use InstallAware Express, your installation script can check the user's system for any packages it requires before blindly reinstalling them.
Distributing packages to other developers
If you distribute run-time or design-time packages to other Delphi developers, be sure to supply .bpl files. You will probably want to include .dcu files as well.