siriusfox/qmk_userspace
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Attempt to compile against Vial too

Browse source
This commit is contained in:
Peter J. A. Cock 2025-06-29 10:51:37 +09:00
parent 1e20a54f63
commit 9fb0585751
3 changed files with 33 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

7
README.md
View file

@ -8,7 +8,7 @@ so that I can experiment with layouts without the overhead of the full
[QMK firmware repository](https://github.com/qmk/qmk_firmware/).
I am also using this to host QMK firmware for any of my own keyboard PCBs (with a
[tweak](/.github/workflows/build_binaries.yaml) to the GitHub Actions
[tweak](.github/workflows/build_binaries.yaml) to the GitHub Actions
`preparation_command` to compile these online):
* [Tutte-Coxeter 36k](keyboards/tutte_coxeter_36k/readme.md) - my no-diode single
@ -16,6 +16,11 @@ I am also using this to host QMK firmware for any of my own keyboard PCBs (with
avoid ghosting. This has a sparse 13x13 scanning matrix (using 26 GPIO pins)
for 36 keys with 6-key rollover (the USB HID limit).
In a further complication, the GitHub Actions setup is duplicated to
[compile my Vial layouts](.github/workflows/build_vial_binaries.yaml) against
the Vial fork of the QMK firmware repository. This uses [vial.json](vial.json)
rather than [qmk.json](qmk.json) to list the layouts to build.
# QMK Userspace
This is a template repository which allows for an external set of QMK keymaps to be defined and compiled. This is useful for users who want to maintain their own keymaps without having to fork the main QMK repository.