geekhack
geekhack Community => Keyboards => Topic started by: geauxflying on Thu, 08 July 2021, 00:31:14
-
About to try out VIAL, but curious to learn what I'm doing wrong here.
I've tried a number of syntax variations. The keymap.c file is created from a JSON export from QMK configurator with encoder code pasted in to the keymap.c. To be sure it wasn't a problem caused by my copy/paste, I tried to compile it based on a direct export from QMK configurator and got the same error.
I ran QMK doctor, it says my setup is fine.
-
I believe you want to provide the directory in which your keymap.c file resides as the option to -km, not the name of the file (which probably needs to be keymap.c).
For example, I have the Ploopy trackball, and I compile with this command:
qmk compile -kb ploopyco/trackball/rev1_005 -km ploopy
And the keymap is found here:
23> ls keyboards/ploopyco/trackball/keymaps/ploopy/
keymap.c readme.md
-
Brilliant... I'll try that! Thank you. What is the significance of the "rev1_005" in your compile command?
-
This particular product had different revisions. If you look under the keyboards directory, there are a lot of different keyboards. The value you provide to the -kb is the path within the keyboards directory to what you want to build. I see boston has no subdirectories under it except for the keymaps. But the Ploopy has a bunch of directories and subdirectories for different products and their revisions.