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 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
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: