You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you want to add a keyboard which doesn't have support for Halcyon modules yet, please follow the [porting guide](docs/PORTING.md). Please follow the [initial setup](#initial-setup--prerequisites) and [build target](#how-to-configure-your-build-targets) steps from this readme first.
24
50
@@ -55,6 +81,7 @@ Before configuring your keymaps or building firmware, you need to set up your bu
55
81
56
82
1.**Start fresh (Optional but recommended):** If you want to start completely from scratch without any default compile options, replace the `qmk.json` in the root folder with the provided `qmk_empty.json`.
57
83
2.**Create your keymap:** Navigate to `keyboards/<keyboard_name>/keymaps` and copy/paste the `default_hlc` or `vial_hlc` folder. Rename it to your desired keymap name.
84
+
*(**Updating Keymaps:** If you modify an existing keymap (e.g., from the original Kyria, Elora, or Aurora), make sure to **add the Halcyon Button mappings** as shown in [the porting guide](docs/PORTING.md#4-define-halcyon-button-mappings))*
58
85
*(If you're unsure what the exact `keyboard_name` is, you can run `qmk list-keyboards | grep <keyboard>`)*
59
86
3.**Add your keymap to the build targets** by running the following command:
60
87
```bash
@@ -120,14 +147,13 @@ For example, to override the `build` job to use the QMK branch:
120
147
If you already have a custom userspace fork of `qmk/qmk_userspace`, you can merge the Splitkb additions manually.
121
148
122
149
#### Option A: Adding the Splitkb Upstream Branch
123
-
1. Add this repo as a remote: `git remote add upstream https://github.com/splitkb/qmk_userspace.git`
124
-
2. Fetch the upstream: `git fetch upstream`
125
-
3. Create a new branch based on our halcyon branch: `git checkout -b halcyon upstream/halcyon`
150
+
1. Add this repo as a remote: `git remote add splitkb https://github.com/splitkb/qmk_userspace.git`
151
+
2. Fetch the upstream: `git fetch splitkb`
152
+
3. Create a new branch based on our halcyon branch: `git checkout -b halcyon splitkb/halcyon`
126
153
4. Make your changes and push: `git push -u origin halcyon`
127
154
128
155
#### Option B: Copying files to your existing branch
129
156
1. Clone or download the files from the Splitkb fork.
130
157
2. Copy `users/halcyon_modules/rules.mk` and the entire `users/halcyon_modules/splitkb/` folder into your personal user folder.
131
-
3. **Updating Keymaps:** If you modify an existing keymap (e.g., from the original Kyria, Elora, or Aurora), make sure to **add 10 new keys** in your keymap matrix. *(Check `keyboards/splitkb/halcyon/kyria/keymaps/default_hlc` for an example).*
132
158
133
159
> **⚠️ Warning:** We use some quantum functions in our userspace. If your existing userspace relies heavily on custom quantum functions, you may encounter compile conflicts. If you restrict yourself to `_user` functions, you should be fine.
0 commit comments