Open sotte opened 2 months ago
It seems that the format of the json file changed: https://docs.qmk.fm/reference_info_json
(Still researching...)
The seemingly invalid values (negative values) for layouts.LAYOUT.layout
prevent the json file from being used. In effect, the usb
properties are not used and VENDOR_ID
etc are not defined.
I think we should update the layout to be in-line with the current format.
My workaround was to delete the offending line or just make the values positive. I don't really use the json file for anything. But this is not the proper solution.
I managed to find some updated code from @patrick-elmquist's fork that I have copied.
This gets everything working again for me. I'm still getting errors, so there's likely more to be done, but this works as a workaround as well.
Just for easier find-ability:
This is the fork: https://github.com/patrick-elmquist/qmk-config-totem
These this is the relevant info.json
: https://github.com/patrick-elmquist/qmk-config-totem/blob/main/info.json
Note that some settings moved from rules.mk
and config.h
into the info.json
.
I should have mentioned the changes you found, as I also made the same changes to the firmware before compiling.
It appears there is still some work to do. In particular, although my code compiles, QMK is upset about layer definitions, and it appears there should be a keyboard.json file as well.
Even though I cloned patricks fork, I'm still getting errors
$ qmk compile -kb totem -km default
Ψ Compiling keymap with gmake -r -R -f builddefs/build_keyboard.mk -s KEYBOARD=totem KEYMAP=default KEYBOARD_FILESAFE=totem TARGET=totem_default VERBOSE=false COLOR=true SILENT=false QMK_BIN="qmk"
☒ totem: LAYOUT: Layout macro should not be defined within ".h" files.
platforms/chibios/platform.mk:266: lib/chibios/os/hal/lib/streams/streams.mk: No existe el fichero o el directorio
gmake: *** No hay ninguna regla para construir el objetivo 'lib/chibios/os/hal/lib/streams/streams.mk'. Alto.
Any help?
This repo does not build with current (as of today) qmk_firmware.
Here are the steps to reproduce it:
Here are the error messages:
I'm a bit lost on how to fix this.