You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

38 lines
2.0 KiB

  1. # QMK CLI :id=qmk-cli
  2. ## Overview :id=overview
  3. The QMK CLI (command line interface) makes building and working with QMK keyboards easier. We have provided a number of commands to simplify and streamline tasks such as obtaining and compiling the QMK firmware, creating keymaps, and more.
  4. ### Requirements :id=requirements
  5. QMK requires Python 3.7 or greater. We try to keep the number of requirements small but you will also need to install the packages listed in [`requirements.txt`](https://github.com/qmk/qmk_firmware/blob/master/requirements.txt). These are installed automatically when you install the QMK CLI.
  6. ### Install Using Homebrew (macOS, some Linux) :id=install-using-homebrew
  7. If you have installed [Homebrew](https://brew.sh) you can tap and install QMK:
  8. ```
  9. brew install qmk/qmk/qmk
  10. export QMK_HOME='~/qmk_firmware' # Optional, set the location for `qmk_firmware`
  11. qmk setup # This will clone `qmk/qmk_firmware` and optionally set up your build environment
  12. ```
  13. ### Install Using pip :id=install-using-easy_install-or-pip
  14. If your system is not listed above you can install QMK manually. First ensure that you have Python 3.7 (or later) installed and have installed pip. Then install QMK with this command:
  15. ```
  16. python3 -m pip install qmk
  17. export QMK_HOME='~/qmk_firmware' # Optional, set the location for `qmk_firmware`
  18. qmk setup # This will clone `qmk/qmk_firmware` and optionally set up your build environment
  19. ```
  20. ### Packaging For Other Operating Systems :id=packaging-for-other-operating-systems
  21. We are looking for people to create and maintain a `qmk` package for more operating systems. If you would like to create a package for your OS please follow these guidelines:
  22. * Follow best practices for your OS when they conflict with these guidelines
  23. * Document why in a comment when you do deviate
  24. * Install using a virtualenv
  25. * Instruct the user to set the environment variable `QMK_HOME` to have the firmware source checked out somewhere other than `~/qmk_firmware`.