Skip to content

Loment 0.1.4.5 QuickFix

Latest

Choose a tag to compare

@FujoJTOP FujoJTOP released this 13 Oct 02:27
· 220 commits to main since this release
bf77a3a

Loment 0.1.4.5 QuickFix

A patch on top of 0.1.4.5. The toolchain
binaries in this package are byte for byte the same as that release's; what changed is the
Windows installer.

What was wrong

Double-clicking setup.exe looked like it did nothing. Measured, it was doing everything: the
package unpacked, install.cmd ran, the toolchain was installed, and the version file was written.
What it never did was show anything — and the console it leaves behind is not visible in that
launch, so "installed correctly" and "nothing happened at all" were the same thing on screen. It also
left cmd processes sitting at pause afterwards.

That is worse than a cosmetic problem: the previous release's headline installer bug was a package
that silently installed nothing, so the reasonable reading of "no window appeared" was that this one
was broken too.

What this release changes

The installer has a face. A window that, on a plain double-click:

  1. fades in a rounded Loment mark and Welcome to Loment;
  2. asks where to install, with the switches it used to bury in README.md as checkboxes
    (PATH, .lomt/.lom file association, the agent guide);
  3. shows the install as it runs — the actual install.ps1 output, streamed line by line;
  4. ends on a receipt: a green check, Loment 0.1.4.5 QuickFix is installed., and the window
    stays open until you close it.

It does not reimplement any of the install: it drives install.ps1 and shows what install.ps1
says. One implementation of the install, two faces.

The command line is untouched. install.cmd with any argument (-Prefix, -NoPath,
-DryRun, -Uninstall, and everything CI uses) takes the console path it always had, with the same
output and the same exit codes. Only a bare double-click — no arguments — opens the window.

A second, quieter fix. The installers now resolve loment and lompi after installing and
name anything earlier on PATH that is not this install. They only ever append to PATH
(deliberately — an installer should not reorder a machine it does not own), so a copy installed
earlier by hand wins silently, and lompi version then reports the older build with nothing
anywhere explaining why.

Install

Asset
loment-0.1.4.5-quickfix-windows-x64-setup.exe Windows x86-64. Double-click; a window walks you through it.
loment-0.1.4.5-quickfix-windows-x64.zip Windows x86-64. Unzip and run install.cmd (same window), or call install.ps1 yourself.
loment-0.1.4.5-quickfix-linux-x64.tar.gz Linux x86-64. Unchanged from 0.1.4.5 — the Linux route always printed what it was doing.
loment-skill.zip The agent guide (SKILL.md) on its own.
SHA256SUMS Checksums. The installers verify the payload against this before copying anything.

Installing and running needs no Python, no clang and no WSL.

Which release to install

  • 0.1.4.5's installer is unchanged and stays published as it is. Its setup.exe does install —
    it just does it invisibly. If you already installed from it, you have this toolchain; nothing needs
    re-installing.
  • 0.1.4's setup.exe is still not being rebuilt
    (#117) — that asset genuinely installs nothing.
    Use the zip, or take this release.

Everything else

There are no other changes. What 0.1.4.5 contains — the four-rung GC ladder and the generational
collector, networking on both targets, lompi 0.2.0 Alpha — and what it does not contain, along
with the known open bugs, are listed in the
0.1.4.5 release notes; that document
still stands as written.