Components v1
Pre-release
Optional Lazarus IDE add-on packages and documentation distributed alongside the Unleashed Installer. Each archive is a snapshot of the upstream project at a version that has been tested with the installer and is known to build and register cleanly inside the IDE.
Where upstream does not bump its own version between snapshots, the archive name carries the upstream commit date and short hash, so a given file name always maps to exactly one upstream commit.
Addons
| Addon | Version | License | Source |
|---|---|---|---|
FWHexView_2.0.16.zip |
v2.0.16 | MIT | https://github.com/AlexanderBagel/FWHexView |
CPUView_1.0_20260711_8fa24fa.zip |
v1.0, snapshot 2026-07-11 | MIT | https://github.com/AlexanderBagel/CPUView |
CPUView_1.0.zip |
v1.0, superseded | MIT | https://github.com/AlexanderBagel/CPUView |
ToggleDisplayAffinity.zip |
v1.0 | MIT | @fibodevy |
MetaDarkStyle_0.9.zip |
v0.9 | Modified LGPL 2.1+ | https://github.com/zamtmn/metadarkstyle |
CPUView_1.0.zip predates the fpdebug split of the Linux x86 register types into a separate unit, so it no longer compiles against current Lazarus on Linux hosts. It is kept for reference only; installers use the dated snapshot above.
Documentation
| Archive | Contents | License | Source |
|---|---|---|---|
doc-chm-fpc3.2.4-laz4.8-0.zip |
RTL / FCL / LCL / LazUtils / prog / ref / user CHM help + .xct cross-reference files, built for FPC 3.2.4 and Lazarus 4.8 |
FPC + Lazarus documentation licenses (fpdoc sources) | https://sourceforge.net/projects/lazarus/files/Lazarus%20Documentation/ |
Mirrored here because the SourceForge link redirects through rotating mirrors, which makes the payload impossible to pin by hash and lets a mirror error page reach the client as a successful download.
How the installer uses these
When the user ticks an addon checkbox, the installer downloads the corresponding zip, verifies its SHA256 against a pinned hash, extracts it under <install>/components-extra/, registers the .lpk files via lazbuild --add-package, and rebuilds the Lazarus IDE so the package is statically linked.
The documentation archive follows the same download + SHA256 path but skips lazbuild entirely: it extracts into <install>/lazarus/docs/, which is where chmhelppkg looks for help content when the user presses F1. The viewer itself (lhelp) is built from the Lazarus sources on every install.
