Issues with QMK configurator when compiling Helix firmware.

[Gazza2000]

When compiling firmware on QMK configurator, repeated errors occur with Helix builds. This prevents the firmware from being downloaded. The following is the error reported in the command window:

|
| .build/obj_helix_rev2_back_oled_default_583be4a/keyboards/helix/rev2/rev2.o: In function matrix_init_kb': | /qmk_compiler/qmk_firmware/keyboards/helix/rev2/rev2.c:25: undefined reference to is_helix_master'
| collect2: error: ld returned 1 exit status
|
makek:300: .build/helix_rev2_back_oled_default_583be4a.elf] Error 1
make: *** akefile:579: helix/rev2/back/oled:default_583be4a] Error 1
�ake finished with errors
�

[mtei]

Known issue.

If I only need to fix the Helix code, I can fix it right away, but unfortunately I need to change the qmk core and it will take some time.

[Mandydeth]

Does this mean there is currently no way to flash a custom keymap?

[amezdraven]

There is but you have to build your keymap by hand in something like notepad++ or such then compile with msys2 or linux terminal.

[Mandydeth]

There is but you have to build your keymap by hand in something like notepad++ or such then compile with msys2 or linux terminal.

I posted another thread above, but I found msys2 generated the same/similar errors. I was able to compile successfully on Linux, with the caveat being that using a .json file when compiling would not allow oled/back lighting to function, whereas building my own keymap did not.

[mtei]

I made a workaround for the compile error on QMK configurator.

Currently the following two targets are compilable.

• helix/pico/qmk_conf (The setting in rules.mk for the keymap level will be ignored.)
• helix/rev2/qmk_conf (The setting in rules.mk for the keymap level will be ignored.)