PDFium Delphi Component Docs

Installation Guide

System Requirements

Installation Steps

  1. Run the installer: Execute PDFiumPas-FULL.exe or PDFiumPas-TRIAL.exe as Administrator
  2. Select IDE integration: On the RAD Studio Integration page, detected Delphi personalities are listed first with the newest version pre-ticked; C++Builder personalities are listed separately and are off by default
  3. Select optional content: Tick C++Builder or Lazarus only when those package files and demo projects should be installed
  4. Choose installation path: Select the directory where components will be installed
  5. Complete installation: Follow the on-screen instructions
  6. Verify installation: The following components will be added to the losLab palette:

Localized Help and Demo Builds

Manual Installation (Advanced)

If automatic installation fails, you can manually install the components:

  1. Copy the component files to your IDE's library path
  2. Add the library path to your IDE's search directories
  3. Install the design-time package through IDE's Package Manager
  4. Rebuild your IDE to register the components

Native Free Pascal and LCL Platforms

Native wrapper builds use an OS and CPU matched Free Pascal compiler, Lazarus/LCL, and PDFium shared library. The qualified configurations use FPC 3.3.1 with LCL 4.99, Qt6 on Linux x86_64, and Cocoa on macOS arm64

Build native executables and units in separate target directories with the selected widget set. Supply the corresponding LCL and lazutils unit paths, and use the compiler's actual target configuration; Windows DCU/PPU files and Windows DLLs cannot be reused as Unix outputs

Set LibraryName to the intended libpdfium.so or libpdfium.dylib path before loading. An ordinary or V8 runtime must match that target and expose the requested features. Missing V8/XFA capabilities remain unavailable features; a library filename does not establish them

System-font access uses fontconfig on Linux and CoreText on macOS; optional CID font subsetting uses HarfBuzz with retained glyph IDs. LCL bitmaps use their actual byte order and channel description, with conversion when the native buffer layout cannot be used directly

Tests/PlatformAcceptance/run_native.py and NativeWrapper.lpr provide source-bound native acceptance for loading, rendering, text, forms, saving, cancellation, and lifecycle checks. Run the target executable on its actual host and retain the report; a readiness inventory or successful cross-compile alone is insufficient

Windows installers and VCL/C++Builder projects remain the Windows setup route. Native Delphi macOS crypto and timestamp helpers are qualified separately from the FPC/LCL visual component

Redistribution

When distributing applications that use PDFium VCL:

Troubleshooting

Common Issues:

Uninstallation

To remove PDFium VCL components:

  1. Use Windows Add/Remove Programs
  2. Or run the uninstaller from the installation directory
  3. Manually remove any remaining files if necessary