gLabels is a program for creating labels and business cards. It works with the sheets of
peel-off labels and card stock sold in office supply shops, and ships a template database
covering more than thirty vendors including Avery, Herma, Zweckform and Dymo. Text, images,
lines, shapes and barcodes can be placed on a label, and a document-merge feature fills them
from a CSV file or address book so an entire sheet can be personalised at once.
Barcode support covers the built-in glbarcode++ symbologies plus zint and libqrencode.
A command line renderer, glabels-batch-qt, produces PDFs without opening the interface.
This package is an unofficial community build of gLabels 4 (glabels-qt), which upstream does
not currently distribute for Windows. It is compiled unmodified from upstream sources by a
public GitHub Actions workflow and is not endorsed by or affiliated with the gLabels project.
Report application bugs upstream and packaging problems to this package's issue tracker.
README
gLabels 4 for Windows
Ready-to-run Windows builds of gLabels 4 — the free label and business-card designer.
Upstream gLabels 4 (glabels-qt) is cross-platform and builds fine on Windows, but the
project does not currently ship Windows binaries — you are expected to install Visual
Studio, Qt, CMake and a handful of libraries and build it yourself.
This repository does that for you, in public, on GitHub's own runners. Every release is
produced by one workflow file from unmodified
upstream sources, so you can read exactly how the binary you downloaded was made — and
reproduce it yourself by forking this repo and pressing Run workflow.
winget — submitted as ibsorn.gLabels, in review at
winget-pkgs#406476. Once merged,
winget install ibsorn.gLabels will work. Not before.
Chocolatey — submitted as
glabels-qt, in moderation. Once approved, choco install glabels-qt will work.
Scoop — not eligible yet. The Extras bucket requires the latest stable
version of a package, and gLabels 4 has no stable release. The manifest is written and
ready in scoop/ for the day upstream tags 4.0.
Compare the result with the matching line in SHA256SUMS.txt.
“Windows protected your PC”
The installer is not code-signed (a certificate costs several hundred euros a year), so
SmartScreen shows a warning the first time. Choose More info → Run anyway, or use the
portable ZIP instead. The SHA-256 sums above, the build log of every release, and the
workflow file are all public so you can check what you are running.
What's inside
Application
gLabels 4 development snapshot (glabels-qt, master)
Toolchain
MSVC 2022, 64-bit, Release
Qt
6.8.x LTS, deployed with windeployqt
Barcodes
built-in glbarcode++, zint and libqrencode
Compressed projects
zlib
Extras
full upstream template database (35+ vendors) and all translations
Also included
glabels-batch-qt.exe, the command-line renderer
Every build runs the upstream unit tests plus a smoke test that renders a PDF from the
packaged tree, so a release can only be published if the deployed binaries actually run.
Status
gLabels 4 is still under active development upstream — there is no final 4.0 release yet.
What you get here are snapshots of the master branch, rebuilt weekly and whenever
upstream changes are picked up. They are usable, but treat them as pre-release software
and keep backups of your projects.
A published release is immutable: the weekly rebuild only publishes when upstream has
actually moved (a new commit count means a new version and a new tag). It never overwrites
the assets of a version that already exists, because a rebuild of the same commit is
byte-different — MSVC and NSIS embed timestamps — and overwriting would change the SHA-256
that the winget and Chocolatey manifests pin.
Building it yourself
Fork this repository and use Actions → Build gLabels for Windows → Run workflow. You
can point it at any upstream branch, tag or commit, and optionally have it publish a
release in your own fork. Nothing besides a GitHub account is required.
Note that the process is reproducible, not the bytes: MSVC and NSIS embed timestamps, so
rebuilding the same commit gives you a working, equivalent binary with a different SHA-256.
The published sums identify a specific release, they are not a build fingerprint.
Any local fixes needed to build a given upstream revision live in patches/
as plain git apply patches, each with a header explaining why it exists and what would
make it removable. The packaging metadata (installer name, icons, file association) lives
in packaging/. No gLabels source code is modified beyond those patches.
Bugs
Something wrong with the installer, packaging, or a missing DLL → open an issue here.
Something wrong with gLabels itself → report it upstream, where the people who can fix it are.
Credits and licence
gLabels is written by Jaye Evins and contributors. This repository contains no gLabels
source code — only build automation — but the binaries it produces are gLabels and are
distributed under the GNU General Public License v3
like the original. The corresponding source for every release is the upstream commit named
in the release notes.
This is an unofficial community build and is not endorsed by or affiliated with the
gLabels project.
