Skip to content

The packages install into the IDE

Choose a tag to compare

@pisarev pisarev released this 15 Aug 16:48
· 3 commits to main since this release

The packages install into the Lazarus IDE. Until now they compiled and then did
nothing: the components never reached the palette.

Three things were missing at once

A package that only declares itself a runtime package is never offered for
installation, and neither of ours declared anything else. Eight units register
components, and none of them said so in the package description, so the IDE had
no reason to call their registration code. And the parser package declared no
dependencies at all - without the unit that provides the registration interface
the IDE would not rebuild.

All three are fixed together, because any one of them alone leaves the same
symptom. Checked the only way that means anything: by installing the packages
into an IDE and placing a component on a form.

The build scripts find their own root

Two build scripts looked for a shared rule at one fixed path. That path exists
in the development tree but not in the published one, so for anyone who
downloaded the repository the step failed instantly. The rule is now looked up
upwards through the tree and works in both layouts.

Each unit builds in its own output directory

The unit-by-unit build put every result into one shared directory. A unit
compiled against one environment then shadowed the same-named unit of another,
and twenty units out of fifty-two failed to build with a message about a system
unit - while each of them built correctly on its own. Every unit now has its own
output directory.

Compatibility

Delphi 37.0 (Delphi 13), win32 and win64
Free Pascal 3.2.2 and 3.3.1, win32 and win64 and linux64