Runtime package linking: EXE starts locally but fails on production

Determining the minimal BPL set for a Delphi EXE

When the Link with runtime packages option is enabled, the executable’s import table contains the names of the BPL DLLs it needs at process start. On a development machine those DLLs are found because RAD Studio adds its \bin folder to the PATH, but on a clean host the Windows loader fails before any user code runs.

Confirmed facts

• The import table can be inspected with any PE‑viewer (dumpbin /imports, PE‑bear, Dependency Walker, or Delphi’s TDump if available).
• The DLL names that appear there correspond exactly to the packages listed in Project Options → Packages for the active configuration, plus any transitive dependencies pulled in by third‑party components.
• Different build configurations (Debug, Release) may enable different conditional defines or component packages, so the imported BPL list can differ.
• Mixing BPLs compiled with different Delphi/RAD Studio versions or update packs is unsafe because the memory manager, exception handling, RTTI layout and package versioning can diverge, leading to access violations or heap corruption even if the EXE starts.

Steps to obtain the minimal required BPL set

1. Open the project in the IDE, select the configuration you want to ship (e.g., Release).
2. Perform a clean build (Build → Clean then Build) to ensure no stale OBJ/DCU files.
3. Locate the resulting EXE in the output folder.
4. Run a PE import dump, for example:

   dumpbin /IMPORTS MyApp.exe

   or use a GUI tool such as PE‑bear and copy the list of DLL names.
5. Filter the output to the names that end in .bpl (or that you know are runtime packages). Those are the BPLs the loader will try to resolve.
6. Compare that list with the Packages list shown in Project Options → Packages for the same configuration; any missing entries indicate transitive dependencies brought in by components.
7. Repeat the clean build and import dump for the Debug configuration. Sort the two DLL lists and diff them; identical lists mean the same runtime‑package references are used.
8. To verify on a clean machine, copy the EXE and the candidate BPLs to a folder that is not on the PATH, run the EXE, and note any “missing DLL” message. Add the reported BPL to the folder and repeat until the loader succeeds before your code runs.

Missing diagnostic detail

The exact set of default runtime packages and their naming scheme varies between Delphi/RAD Studio versions and editions (Professional, Enterprise, Architect). Knowing your specific version and edition would let us confirm whether the typical RTL/VCL/BDE/etc. BPLs are present or if additional product‑specific packages are required. Please provide the Delphi/RAD Studio version (e.g., 11.2 Alexandria) and edition you are using.