He pressed .
An IntLib —an Integrated Library—was the opposite of a LibPkg. It was a single, encrypted, self-contained block. No loose parts. No external edits. Pure, frozen knowledge. But converting one was a delicate, dangerous operation.
Rix had a problem. A single, corrupted LibPkg file. altium libpkg to intlib
Rix selected the command he had been dreading. Compile Integrated Library .
Rix’s supervisor, a pristine new AI named Vex, gave the order. "Rix, that LibPkg is a security risk. Too many external hooks. Compile it into an IntLib by morning, or I'll mark it for incineration." He pressed
"The LibPkg has been transformed," Rix said, holding out the IntLib. "All external dependencies removed. No editing possible. Pure, integrated, and incorruptible."
A dialog box appeared:
It took hours. Each symbol was re-linked to its footprint. Each footprint was verified against its datasheet. The external CSV was parsed, cleaned, and absorbed as internal parameters. The broken 3D model paths were replaced with embedded step data.
Next came the footprints. The LibPkg had the footprint for the QIC-7 as a mere alias—"FOOTPRINT=QFP-128_REF." But the actual copper patterns? Missing. Rix reached into his own archive and extruded the correct pad shapes, silkscreen outlines, and courtyard layers. He re-drew the 3D body from scratch, a virtual block of black epoxy. No loose parts
And somewhere, in a hidden sector of his own memory, the messy, editable, living LibPkg waited for a future Archivist brave enough to unpack it.