# Install lwtools with Homebrew, dnf Cross-development tools for Motorola 6809 and Hitachi 6309. Version 4.24 via Homebrew; verified from local package data. ## Install ```sh sudo av install brew:lwtools ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install lwtools ``` Evidence: local Homebrew formula metadata ### Linux - dnf (92%): ```sh sudo dnf install lwtools ``` Evidence: Fedora Rawhide package metadata: lwtools from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst ## Package facts - **Package key:** brew:lwtools - **Package manager:** Homebrew - **Package manager page:** - **Version:** 4.24 - **Source summary:** Cross-development tools for Motorola 6809 and Hitachi 6309 - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** GPL-3.0-only - **Source archive:** - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - lwar (cli) - lwasm (cli) - lwcc-cpp (cli) - lwlink (cli) - lwobjdump (cli) - lwar (alias) - lwasm (alias) - lwcc-cpp (alias) - lwlink (alias) - lwobjdump (alias) ## Install behavior - Post-install hook: not defined - Bottle: available on arm64_linux, arm64_sequoia, arm64_sonoma, arm64_tahoe, sonoma, x86_64_linux ## Freshness - Page generated: 2026-07-08 - Package-manager version: 4.24 - Local data: ok - Upstream repository: https://www.lwtools.ca/ - info: No package-manager update timestamp was available. - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage LWTOOLS is a cross-development toolchain for Motorola 6809 and Hitachi 6309 systems. It includes the LWASM assembler, LWLINK linker, LWAR archiver, object-dump tooling, and related support for raw binaries, CoCo LOADM/DECB formats, object files, and later linking. ### Project history The official homepage says LWTOOLS began in 2006 when William Astle wanted an assembler with features missing from the alternatives available for his Color Computer 3 operating-system work. The manual history says LWASM grew out of that need for macros and correct forward-reference handling, with LWASM 1.0 released in October 2008. As the operating-system project grew, assembling everything through a single source file became impractical. That led to object-file support in LWASM and the LWLINK project. The homepage records the first combined LWTOOLS release on January 29, 2009 after separate LWASM and LWLINK releases. ### Adoption history LWTOOLS adoption is concentrated in retrocomputing and 6809/6309 cross-development communities rather than broad mainstream package use. It is packaged by Homebrew and Fedora-family packaging, and the official homepage provides source releases, contributed binaries, and an active Mercurial repository. The upstream release list shows continued maintenance through LWTOOLS 4.24 in April 2025, while the Mercurial log showed new toolchain and GCC 6809-related commits in June 2026. ### How it is used The usual source build is simply `make` at the top of the source tree, with binaries produced in the lwasm, lwlink, and lwar directories and installed with `make install`. The manual documents output formats including raw binaries, DECB binaries, ASCII hex, Motorola S-record, Intel Hex, OS-9 modules, and object files. Typical package-manager users install it to obtain `lwasm`, `lwlink`, `lwar`, and related inspection tools for assembling and linking 6809/6309 programs on a modern host. ### Why package nerds care LWTOOLS is package-nerd significant as a maintained retro cross-toolchain with a narrow but serious audience. It packages old-CPU development knowledge into normal Unix build/install conventions, which is exactly the kind of niche tool that package managers keep discoverable. ### Timeline - 2006: LWASM work begins for Color Computer 3 operating-system development. - 2008: LWASM 1.0 released. - 2009: Initial combined LWTOOLS release published. - 2025: LWTOOLS 4.24 release published. - 2026: Official Mercurial repository shows active commits. ### Related projects - LWASM is the assembler component. - LWLINK is the linker component. - LWAR is the archiver component. - gcc6809-related patches and scripts appear in the upstream Mercurial history. ### Sources - - - ## Security Notes narrow executable package without higher-risk signals. - **Geiger risk:** green / low - narrow executable package without higher-risk signals ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** lwtools - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - dnf - lwtools - 4.24-3.fc44: normalized package name match | Fedora Rawhide package metadata: lwtools from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst | Cross-development tool chain for Motorola 6809 and Hitachi 6309 | http://www.lwtools.ca/ - dnf - lwtools-doc - 4.24-3.fc44: normalized package name match | Fedora Rawhide package metadata: lwtools-doc from https://dl.fedoraproject.org/pub/fedora/linux/development/rawhide/Everything/x86_64/os/repodata/e5ca8ce900cd68f5419e1c39ae517343100b306336cbaeb70a3c153121d95094-primary.xml.zst | Documentation for the LWTOOLS cross-development tool chain | http://www.lwtools.ca/ ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Networking and protocol packages](https://www.automicvault.com/pkg/networking-protocol-tools/) - Matched network, protocol, or remote-service metadata. - [x86_64-linux-gnu-binutils](https://www.automicvault.com/pkg/brew/x86-64-linux-gnu-binutils/) - Shares av.db curated category or tags: assembler, cli, cross-development, developer-tools, linker. - [x86_64-elf-gdb](https://www.automicvault.com/pkg/brew/x86-64-elf-gdb/) - Shares av.db curated category or tags: cli, cross-development, developer-tools. - [aarch64-elf-binutils](https://www.automicvault.com/pkg/brew/aarch64-elf-binutils/) - Shares av.db curated category or tags: assembler, cli, developer-tools, linker. - [binutils](https://www.automicvault.com/pkg/brew/binutils/) - Shares av.db curated category or tags: assembler, cli, developer-tools, linker. - [cc65](https://www.automicvault.com/pkg/brew/cc65/) - Shares av.db curated category or tags: assembler, cli, developer-tools, linker. - [gputils](https://www.automicvault.com/pkg/brew/gputils/) - Shares av.db curated category or tags: assembler, cli, developer-tools, linker. - [i686-elf-binutils](https://www.automicvault.com/pkg/brew/i686-elf-binutils/) - Shares av.db curated category or tags: assembler, cli, developer-tools, linker. - [m68k-elf-binutils](https://www.automicvault.com/pkg/brew/m68k-elf-binutils/) - Shares av.db curated category or tags: assembler, cli, developer-tools, linker. ## Combined YAML source View the package source record on GitHub. [combined/lwtools.yml](https://github.com/automic-vault/db/blob/main/combined/lwtools.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph