-
-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Compile fails. #28
Comments
I've got the same errors did you find the answer? |
What I had to do was abandon the 2040 (folder) command and do qmk make -kb klor -km default -e CONVERT_TO=promicro. |
Hi, Thanks for trying to assist. I tried the make command but it didn't seem to do much other than give me a QMK.exe: error. ================================= ☒ Not including data from file: keyboards/klor/info.json
builddefs/converters.mk:28: *** Converting from 'promicro' to 'promicro' not possible!. Stop.My end goal is to try and get a compiled Vial version for a Sea Picro RP2040 Controller, if you have any more thoughts or can point me to a working version of the files needed that would be helpful |
If you extract it as klor2 it won't screw up any of your original files. |
Hi pokey - I tried running the pokey keymap and got the following :( [dm@hhhhh QMK_files]$ qmk compile -kb klor -km pokey ☒ Not including data from file: keyboards/klor/info.json Generating: .build/obj_klor_pokey/src/info_config.h [WARNINGS] |
Hmmm. Maybe it I forgot that I modified the json? Are you running everything as an administrator? Pretty much have to do the entire process from installing QMK to running the keyboard make commands. |
☒ Not including data from file: keyboards/klor/info.json
☒ layouts.LAYOUT_yubitsume.layout.20.x: -0.5 is less than the minimum of 0
☒ klor/2040: RGB_DI_PIN in config.h is no longer a valid option and should be replaced with WS2812_DI_PIN or APA102_DI_PIN
☒ Invalid API data: klor/2040: haptic.driver: 'DRV2605L' is not one of ['drv2605l', 'solenoid']
builddefs/converters.mk:22: *** Converting to 'promicro_rp2040' not possible!. Stop.
The text was updated successfully, but these errors were encountered: