this post was submitted on 08 Jul 2023
9 points (100.0% liked)

ErgoMechKeyboards

5820 readers
3 users here now

Ergonomic, split and other weird keyboards

Rules

Keep it ergo

Posts must be of/about keyboards that have a clear delineation between the left and right halves of the keyboard, column stagger, or both. This includes one-handed (one half doesn't exist, what clearer delineation is that!?)

i.e. no regular non-split¹ row-stagger and no non-split¹ ortholinear²

¹ split meaning a separation of the halves, whether fixed in place or entirely separate, both are fine.
² ortholinear meaning keys layed out in a grid

No Spam

No excessive posting/"shilling" for commercial purposes. Vendors are permitted to promote their products/services but keep it to a minimum and use the [vendor] flair. Posts that appear to be marketing without being transparent about it will be removed.

No Buy/Sell/Trade

This subreddit is not a marketplace, please post on r/mechmarket or other relevant marketplace.

Some useful links

founded 1 year ago
MODERATORS
 

So I'm trying to follow the instructions from the old reddit community to build the miryoku firmware for [seeeduino_xiao_ble, chiper36, Colemak, default, Mac, flip, default, default, default, default].

https://www.reddit.com/r/ErgoMechKeyboards/comments/12tvpsf/workflow_build_for_miryoku_with_the_revxlp_and/

But I'm new to github and don't quite get it. How do I select zmkfirmware/zmk/main build actions? I only see master as an option.

you are viewing a single comment's thread
view the rest of the comments
[–] hyperreal 5 points 1 year ago (1 children)

Have you checked out the quickstart guide? You need to fork manna_harbour/miryoku_zmk and use the workflow found in Actions > Build Inputs.

Personally, I prefer to take manna_harbour's excellent miryoku layout as a basis and write my own keymap, using the existing documentation as a guide. There's alot more trial and error but you'll have a better understanding of how the firmware works when you've got it working. I find the GitHub Actions-based workflow for building firmware overly complicated for my personal use case.

[–] MediaRefugee 2 points 1 year ago

Yes, I cloned the repo and tried build inputs, but the build fails with the same issue the poster in the other thread has, apparently related to seeeduino_xiao_ble boards. Manna_harbour said:

The shield has been updated to use ZMK main now, so the outboard will need updating. For now you can use zmkfirmware/zmk/main with the workflow branches option to override the old value.

But I don't see how to do this. Master is the only option when I use the build inputs action.

I did try making my own similar layout with vial before, but my new board uses zmk and setting everything up by hand looks very fussy when I could just use an existing firmware that does what I want. .... If I can get it to build, anyway.