PDFiumPas-FULL.exe or PDFiumPas-TRIAL.exe as AdministratorDocs assets and then copies only the help language folders selected by the Windows locale name and UI language LCIDen-GB for supported British, Commonwealth, and Caribbean English locales; en-US is used for other English locales and as the fallback when no regional help set matcheses for Spain-style locales and es-419 for Latin American locales; Chinese help is split between zh-cn and zh-twIf automatic installation fails, you can manually install the components:
Native wrapper builds require Free Pascal, Lazarus/LCL and a PDFium shared library matching the host OS and CPU. Qualified configurations use FPC 3.3.1 and LCL 4.99, with Qt6 on Linux x86_64 or Cocoa on macOS arm64
Build each target's executables and units in its own directory using the chosen widget set. Provide matching LCL and lazutils unit paths and the compiler's real target configuration; Windows DCU/PPU files or DLLs cannot serve as Unix output
Before loading, set LibraryName to the intended libpdfium.so or libpdfium.dylib. Both ordinary and V8 runtimes must match the target and export the requested features; absent V8/XFA capabilities stay unavailable, regardless of the library's filename
Linux system fonts are accessed through fontconfig and macOS fonts through CoreText; optional CID subsetting uses HarfBuzz whilst retaining glyph IDs. LCL bitmap handling follows actual byte order and channel descriptions, converting when a native buffer 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. Execute the target binary on its actual host and keep its report; an inventory of readiness or a successful cross-compile is not sufficient
Windows installers and VCL/C++Builder projects remain the Windows installation route. Native Delphi macOS crypto and timestamp helper qualification is separate from the FPC/LCL visual component
When distributing applications that use PDFium VCL:
DLLs\Win32\pdfium.dll or DLLs\Win64\pdfium.dll tree beside your application or in a parent application folderDLLs\Win32\pdfium.v8.dll or DLLs\Win64\pdfium.v8.dll in the same DLLs tree and set EnableV8Engine before loadingDLLs\Win32 or DLLs\Win64, or directly in the application pathpdfium.v8.dll is available in the platform DLLs folder and EnableV8Engine is set before loadingTo remove PDFium VCL components: