crystal-qt6
crystal-qt6
crystal-qt6 is a Qt6 bindings project for Crystal with an explicit, incrementally growing API for desktop applications.
This repository currently provides:
- a native Qt6 bridge compiled from C++
- an idiomatic Crystal wrapper for common widget tasks
- reusable object, timer, signal, and event-hook primitives for richer bindings
- runnable examples
- a spec suite that exercises the wrapper end to end
Status
This is an initial, working foundation rather than a full binding of the entire Qt6 API. The current surface now covers the basics for custom widgets plus a reduced desktop application shell built around main windows, menus, actions, docks, toolbars, dialogs, and a few common controls.
Requirements
- Crystal 1.11+
- Qt6 Widgets and Qt6 Svg development packages available through
pkg-config - macOS with Homebrew Qt6 works out of the box when
pkg-configcan resolveQt6WidgetsandQt6Svg - Linux distributions using GCC's standard C++ runtime, such as Fedora with
qt6-qtbase-devel, are supported
The Crystal FFI layer links against the platform's default C++ runtime:
- macOS:
libc++ - Linux:
libstdc++
Build
The native Qt shim builds automatically the first time you compile, run, or spec the shard. You can still build it explicitly:
make native
If you need to disable the automatic build, set QT6CR_SKIP_BUILD=1 before invoking Crystal and build the shim yourself with make native.
Run the full test suite:
make spec
Run the examples:
make example-hello
make example-counter
make example-shell
make example-events
make example-render
Direct Crystal commands also work without a separate native build step:
crystal run examples/hello_world.cr
crystal spec
Example highlights:
examples/hello_world.cr: smallest possible window with a label and buttonexamples/counter.cr: simple stateful widget wiring with button callbacksexamples/editor_shell.cr:QMainWindow, menus, actions, action groups, shortcuts, toolbars, docks, convenience dialog helpers, and form/grid layout compositionexamples/event_monitor.cr:QTimerplusEventWidgetresize, paint, mouse, wheel, and key hooksexamples/rendering_stack.cr: offscreen rendering plus SVG import/export and PDF export withQImage,QPixmap,QSvgGenerator,QSvgRenderer,QPdfWriter,QPainter,QPainterPath, andQTransform
Continuous Integration
GitHub Actions runs the native build, spec suite, and example compilation on both macOS and Linux via .github/workflows/ci.yml.
The Linux job uses xvfb with Qt's xcb platform plugin for headless widget tests so CI behaves like a normal X11 desktop session without the offscreen plugin warnings. The macOS job installs Homebrew Qt and runs the same specs with QT_QPA_PLATFORM=offscreen.
API Overview
require "qt6"
app = Qt6.application
count = 0
window = Qt6.window("Counter", 320, 140) do |widget|
widget.vbox do |column|
value = Qt6::Label.new(count.to_s)
button = Qt6::PushButton.new("Increment")
button.on_clicked do
count += 1
value.text = count.to_s
end
column << value
column << button
end
end
window.show
app.run
Current Binding Surface
Qt6.applicationfor creating or reusing a singleQApplicationQt6.windowfor quick top-level window setupQt6::QObjectas the common wrapper base for owned Qt objectsQt6::Signalfor Crystal-side callback compositionQt6::QTimerfor timeout-driven work on the Qt event loopQt6::Color,Qt6::PointF,Qt6::Size, andQt6::RectFfor common value typesQt6::QImage,Qt6::QPixmap,Qt6::QSvgGenerator,Qt6::QSvgRenderer,Qt6::QPdfWriter,Qt6::QPainter,Qt6::QPainterPath,Qt6::QTransform,Qt6::QPen,Qt6::QBrush,Qt6::QFont,Qt6::QFontMetrics,Qt6::QFontMetricsF, andQt6::ImageFormatfor raster, SVG, and PDF renderingQt6::Widgetfor generic widgets and top-level windowsQt6::MainWindow,Qt6::Dialog, andQt6::DockWidgetfor desktop application shellsQt6::MessageBox,Qt6::FileDialog,Qt6::ColorDialog, andQt6::InputDialogfor standard dialogs- convenience helpers such as
MessageBox.information,MessageBox.question,ColorDialog.get_color, andInputDialog.get_text/get_int/get_double Qt6::InputDialogInputModeplus message-box and file-dialog enums for dialog configurationQt6::MenuBar,Qt6::Menu,Qt6::ToolBar,Qt6::StatusBar,Qt6::Action, andQt6::ActionGroupfor shell compositionQt6::KeySequenceandQActionshortcuts for keyboard-driven commandsQt6::EventWidgetfor custom widget event hooksQt6::Labelfor text displayQt6::PushButtonfor push buttons and click callbacksQt6::LineEdit,Qt6::CheckBox, andQt6::ComboBoxfor common form controlsQt6::VBoxLayout,Qt6::HBoxLayout,Qt6::FormLayout, andQt6::GridLayoutfor layout composition
Testing Strategy
The specs cover:
- process shutdown behavior on macOS so teardown stays free of the
QThreadStorageexit warning - standard dialog configuration for
QMessageBox,QFileDialog,QColorDialog, andQInputDialog - convenience helper flows for message, color, and input dialogs
- layout composition through vertical, horizontal, form, and grid layouts
- raster, SVG, and PDF rendering with images, pixmaps, painter paths, transforms, SVG generators, and PDF writers
QObjectdestruction signals andQTimertimeout delivery- geometry accessors and custom widget paint, resize, mouse, wheel, and key event hooks
- reduced application-shell wiring for actions, menus, toolbars, dialogs, docks, status bars, and common controls
- widget lifecycle and visibility state
- title and text round trips through the native bridge
- layout composition
- button click callbacks routed from Qt into Crystal blocks
That gives the project an executable contract for both the C++ shim and the Crystal wrapper.
Lifecycle Notes
Qt objects must be created and destroyed on the GUI thread. The bindings therefore avoid GC finalizers for Qt teardown and instead perform deterministic cleanup during process exit through Qt6.shutdown.
You can call Qt6.shutdown yourself if you want an explicit shutdown point, but ordinary applications can rely on the built-in exit hook.
Project Layout
src/qt6.cr: public Crystal APIsrc/qt6/native.cr: FFI declarationsext/qt6cr/include/qt6cr.h: C ABI for the shimext/qt6cr/src/qt6cr.cpp: Qt6 bridge implementationspec/qt6_spec.cr: end-to-end specsexamples/: sample applicationsdocs/design.md: architecture notesdocs/crystal-qt6-roadmap.md: phased roadmap for growingcrystal-qt6toward larger application ports
Extending The Bindings
The next logical additions are:
- more layouts such as
HBoxLayout, grid layouts, and form layouts - shell refinements such as shortcuts, action groups, and standard dialogs
- additional common controls such as radio buttons, list widgets, trees, tabs, and splitters
- widget paint-device integration, plus pen/brush/font refinements on top of the current rendering stack
crystal-qt6
- 1
- 0
- 0
- 0
- 0
- about 2 hours ago
- April 8, 2026
Thu, 09 Apr 2026 10:43:12 GMT