DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to build release binaries for six OS and CPU targets with LLM Visuals

Cross-compile archives for Linux, macOS and Windows on x86-64 and ARM64 from one machine.

Who it is forA maintainer who ships a Rust CLI and needs binaries for every platform without a separate build machine for each.

The problemProducing and testing binaries for three operating systems and two CPU families by hand is slow and error-prone.

The outcomeArchives for each supported target written to a dist folder on the local machine.

What you need first

  • Rust toolchain 1.75 or newer
  • A C compiler, needed by the bundled SQLite used for --log-db
  • A locally listening llama-server for throughput panels (the demo mode needs none)
  • nvidia-smi for NVIDIA GPU panels, xpu-smi for Intel, the amdgpu driver for AMD, or macmon on Apple silicon

Steps

  1. Install a Rust toolchain (1.75 or newer) and a C compiler, since SQLite is compiled from bundled C source.
  2. Run git clone https://github.com/DingoOz/llm-visuals and cd llm-visuals.
  3. Run ./scripts/cross-build.sh to build every target the host can link.
  4. Check the archives written to dist/ and compare the set against the six-target table in the README.

Prompt for your agent

Using the repo DingoOz/llm-visuals, run `./scripts/cross-build.sh` from the repo root. Expected output: archives for each target this host can link, written to dist/. Verify the count of archives matches the number of targets the script reports as buildable.

Caveat. Some targets need toolchains the host may lack, so the script builds only what this host can link, and the README says Windows and macOS targets are built on their own runners in CI.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page