XWord miscellaneous preferences for crossword program behaviour.
Miscellaneous preferences for everyday crossword client behaviour. XWord docs/images from mrichards42/xword (GPL-3.0).

The current tag for mrichards42/xword ships XWord-Windows.exe and XWord-macOS.zip only. Linux users follow the README build section with premake5 and wxWidgets. This guide records that path as UNVERIFIED until a real machine run is logged in research notes.

Steps (from upstream docs)

  1. Read the README build section.
  2. Install wxWidgets development packages for your distro.
  3. Install premake5 and other listed dependencies.
  4. Run premake5 gmake then make as upstream shows.
  5. Launch the resulting binary and open a .puz.

Exact package manager lines differ across Debian, Fedora, and Arch. Record what worked on your distro. Do not invent a Flatpak id for a crossword client that does not publish one.

Why no binary

Upstream focused Releases assets on Windows and macOS for current release. Changelog entries still mention Linux fixes historically, which is why a source build remains plausible. Prefer Windows or macOS desks when a lab needs a one-click crossword installer today.

After a successful build

Write the commit hash, wxWidgets version, and binary path on the ticket. Prefer rebuilding from a known tag when you update. Safe habits for other OS doors: download safe. First run: first run.

Common mistakes

Expecting an AppImage on the Releases page. Copying a Windows exe into Wine without documenting it. Skipping dependency versions on the ticket. Mixing a personal fork without checking upstream tags. Teaching a class before one local open works.

Shared desk pin

Shared desks should pin the Releases URL beside the OS version. After every reimage, prove one local crossword open before workshops begin. Travel laptops should download once on a trusted network, then solve offline with puzzles already on disk.

Club download discipline

Club volunteers invent Softonic mirrors when a first launch is blocked. Prefer returning to GitHub Releases for mrichards42/xword instead. Write the exact filename on the machine ticket so the next bump stays honest for the whole room.

Classroom images

Classroom images drift when someone keeps a private copy of an old exe. Prefer the current tag that still ships XWord-Windows.exe and XWord-macOS.zip together. Linux builders should document their wxWidgets version beside the commit they built.

Family PCs

Family PCs benefit from a boring puzzle folder path. Keep Across Lite or a browser board as a fallback until the new window feels normal. Subscription newspaper apps remain optional for archives and are a different job than a local .puz client.

Publisher note

Across Bind publishes install maps for people who searched for crossword software. Upstream XWord remains GPL-3.0. When Releases change asset names, re-check the live list before you refresh a lab image.

Desk logistics

  • Ticket line: OS, asset name, puzzle folder
  • Demo door: one official path for volunteers
  • Travel rule: trusted network first

Write the OS version, asset name, and puzzle folder on one ticket line. Clubs should assign a single demo door so volunteers stop mixing Across Lite, browser tabs, and XWord without notes. Travel kits should carry puzzles on disk only when policy allows encrypted storage.

After the first week

Only then add Package Manager downloaders, heavy layout floating, or diagramless drills. Prefer one documented update habit. Re-check Releases whenever upstream publishes a new tag that still lists your OS asset.

Frequently asked questions

Is there a Linux AppImage for crossword?

No Linux AppImage, Flatpak, or .deb shipped on mrichards42/xword the current tag. Prefer a source build from the README, or use Windows and macOS Releases assets on machines that can run those installers instead.

What does the Linux build need?

Upstream documents wxWidgets, LuaJIT, expat, curl, and related libraries plus premake5. Exact package names vary by distro. Record what you installed beside the commit hash on the machine ticket for later rebuilds.

Should I invent a Flatpak id?

No. Do not invent Snap, Flatpak, or apt package ids that were not found on this review date. Prefer the documented source path or the official Windows and macOS binaries for other desks.