[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
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

Slow compilation speed on windows MSYS #13662

Closed
xsrvmy opened this issue Jul 23, 2021 · 12 comments
Closed

Slow compilation speed on windows MSYS #13662

xsrvmy opened this issue Jul 23, 2021 · 12 comments
Labels
help wanted question stale Issues or pull requests that have become inactive without resolution.

Comments

@xsrvmy
Copy link
xsrvmy commented Jul 23, 2021

I have recently switch back to using windows again and have downloaded the MSYS version of QMK. I have noticed that compilation is extremely slow. There is an extremely long delay between calling qmk flash and the message stating which layout is being compiled, and another shorter delay between that and the first file compilation message. Compilation itself also seemed to be slow. Is this expected because MSYS is slow, or is there a problem in the firmware?

@daskygit
Copy link
Member

This is pretty normal, if you want faster compilation try QMK WSL. It's a little more complex to setup but works well.

@zvecr
Copy link
Member
zvecr commented Jul 23, 2021

Is this expected because MSYS is slow, or is there a problem in the firmware?

Expected and partially being tracked in qmk/qmk_distro_msys#23

@xsrvmy
Copy link
Author
xsrvmy commented Jul 23, 2021

Is WSL faster? And can you flash with WSL2 now or do I have to use QMK toolbox?

@fauxpark
Copy link
Member

WSL is much faster (it's essentially a Linux VM), as long as you keep the qmk_firmware repo inside the WSL filesystem: microsoft/WSL#4197

@Ciantic
Copy link
Ciantic commented Jul 24, 2021

You can also use Docker to compile, and flash with teensy_loader_cli.exe (depending on your keyboard).

I have example with that. It also includes a vscode .devcontainer environment, so if you use VSCode you can also use C++ environment with all the goodies. https://github.com/Ciantic/CianticQmkKeymap

@xsrvmy
Copy link
Author
xsrvmy commented Jul 26, 2021

Decided to setup QMK in WSL and yeah it is basically as fast as my linux boot. Only annoyance is having to flash with toolbox. I got VIA working though I can use that to fiddle around.

@daskygit
Copy link
Member

You should be able to flash most things using the QMK WSL distro I linked earlier.

@drashna
Copy link
Member
drashna commented Jul 31, 2021

Also, make sure that you're using WSL version 2, if your system supports it. v1 is okay, as it is faster than MSYS. However, version 2 is a LOT faster.

@elfmimi
Copy link
Contributor
elfmimi commented Aug 1, 2021

Since while ago, savvy users have started using command like this. @xsrvmy
make preonic/rev3:default:flash DFU_UTIL=/mnt/c/QMK_MSYS/mingw64/bin/dfu-util.exe
within arbitrary WSL2 environment + QMK_MSYS or QMK-Toolbox installed to the host environment.

#13431 (comment)

@drashna
Copy link
Member
drashna commented Aug 9, 2021

Since while ago, savvy users have started using command like this. @xsrvmy
make preonic/rev3:default:flash DFU_UTIL=/mnt/c/QMK_MSYS/mingw64/bin/dfu-util.exe
within arbitrary WSL2 environment + QMK_MSYS or QMK-Toolbox installed to the host environment.

#13431 (comment)

That's ... effectively what QMK WSL is doing. 😆

@stale
Copy link
stale bot commented Jan 9, 2022

This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug, in progress, on hold, discussion or to do to prevent the issue from being re-flagged.

@stale stale bot added the stale Issues or pull requests that have become inactive without resolution. label Jan 9, 2022
@stale
Copy link
stale bot commented Apr 17, 2022

This issue has been automatically closed because it has not had activity in the last 30 days. If this issue is still valid, re-open the issue and let us know.

@stale stale bot closed this as completed Apr 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted question stale Issues or pull requests that have become inactive without resolution.
Projects
None yet
Development

No branches or pull requests

7 participants