mirror of
https://github.com/Keychron/qmk_firmware.git
synced 2024-12-02 05:37:00 +06:00
b272c035ba
* fix CLI section links in the Summary * fix heading in Pointing Device doc * fix headings in PS/2 Mouse Support doc * add explicit section ids to I2C Master Driver doc * reformat GPIO Controls table Much like the I2C Master Driver doc, I found this a bit less than ideal to read. (The table was actually wider than the space available for it.) Reformatted so each GPIO function is an H3 heading, followed by a paragraph and a table of each architecture's old-style function. * migrate changes from I2C Master Driver doc to Japanese translation * add explicit anchors to I2C Master Driver docs * fix code block language markers The language markers are case-sensitive; using the wrong case means the syntax highlighting doesn't work. Good: ```c Bad: ```C * restore Japanese I2C Master Driver doc to current master Can't update the internal tracking references accurately until the changes to the English doc are committed to master. * add explicit anchors to edited files * change ChibiOS/ARM to ARM/ChibiOS Because ARM/ATSAM is also a thing that exists. * fix code block language markers again Used the wrong markers in a few spots. Also these are apparently always supposed to be lowercase. * add section anchors to cli.md * restore table formatting on GPIO Control doc * remove changes to _summary.md
40 lines
1.9 KiB
Markdown
40 lines
1.9 KiB
Markdown
# QMK CLI :id=qmk-cli
|
|
|
|
## Overview :id=overview
|
|
|
|
The QMK CLI 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.
|
|
|
|
### Requirements :id=requirements
|
|
|
|
The CLI requires Python 3.5 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.
|
|
|
|
### Install Using Homebrew (macOS, some Linux) :id=install-using-homebrew
|
|
|
|
If you have installed [Homebrew](https://brew.sh) you can tap and install QMK:
|
|
|
|
```
|
|
brew tap qmk/qmk
|
|
brew install qmk
|
|
export QMK_HOME='~/qmk_firmware' # Optional, set the location for `qmk_firmware`
|
|
qmk setup # This will clone `qmk/qmk_firmware` and optionally set up your build environment
|
|
```
|
|
|
|
### Install Using easy_install or pip :id=install-using-easy_install-or-pip
|
|
|
|
If your system is not listed above you can install QMK manually. First ensure that you have python 3.5 (or later) installed and have installed pip. Then install QMK with this command:
|
|
|
|
```
|
|
pip3 install qmk
|
|
export QMK_HOME='~/qmk_firmware' # Optional, set the location for `qmk_firmware`
|
|
qmk setup # This will clone `qmk/qmk_firmware` and optionally set up your build environment
|
|
```
|
|
|
|
### Packaging For Other Operating Systems :id=packaging-for-other-operating-systems
|
|
|
|
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:
|
|
|
|
* Follow best practices for your OS when they conflict with these guidelines
|
|
* Document why in a comment when you do deviate
|
|
* Install using a virtualenv
|
|
* Instruct the user to set the environment variable `QMK_HOME` to have the firmware source checked out somewhere other than `~/qmk_firmware`.
|