qmk_firmware - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	[CLI] Add a subcommand for getting information about a keyboard (#8666)	Zach White	2020-05-26	1	-0/+1
\| \| \| \| \|	You can now use `qmk info` to get information about keyboards and keymaps. Co-authored-by: Erovia <Erovia@users.noreply.github.com>
*	CLI: Use `shutil.which` to detect gmake, instead of OS check.	Pete Johanson	2020-04-13	1	-5/+2
\|
*	CLI: Invoke gmake on FreeBSD when using `qmk compile`.	Pete Johanson	2020-04-13	1	-1/+6
\| \| \| \|	* Current makefiles aren't portable, so invoke gmake on FreeBSD.
*	CLI: More MSYS2 fixes (#8577)	Erovia	2020-03-29	1	-0/+20
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* CLI: More MSYS2 fixes Now I can fully setup and work with qmk_firmware on an MSYS2 installation without any errors or exceptions. * Apply suggestions from code review Co-Authored-By: skullydazed <skullydazed@users.noreply.github.com> * Some improvements * Remove unnecessary import * Remove slow, unused code Getting the version from GIT was slow on both Windows and Docker. Until we find a better, faster way, this is removed. * remove unused imports * Implement @vomindoraan's suggestions * refine how we pick the shell to use * Apply @fauxpark's suggestions fauxpark investigated the topic of shells in MSYS2 a bit and we come to the conclusion that the safest bet was to just use the user's shell. Anything more just opens up more edge-cases than it solves. Co-Authored-By: Ryan <fauxpark@gmail.com> * Use `platform_id` in doctor This will bring it in line with the new code. Co-authored-by: skullydazed <skullydazed@users.noreply.github.com> Co-authored-by: skullY <skullydazed@gmail.com> Co-authored-by: Ryan <fauxpark@gmail.com>
*	Add decorators for determining keyboard and keymap based on current ↵	skullydazed	2020-03-13	1	-69/+0
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	directory (#8191) * Use pathlib everywhere we can * Improvements based on @erovia's feedback * rework qmk compile and qmk flash to use pathlib * style * Remove the subcommand_name argument from find_keyboard_keymap() * add experimental decorators * Create decorators for finding keyboard and keymap based on current directory. Decorators were inspired by @Erovia's brilliant work on the proof of concept.
*	Use pathlib everywhere we can (#7872)	skullydazed	2020-02-17	1	-9/+87
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	* Use pathlib everywhere we can * Update lib/python/qmk/path.py Co-Authored-By: Erovia <Erovia@users.noreply.github.com> * Update lib/python/qmk/path.py Co-Authored-By: Erovia <Erovia@users.noreply.github.com> * Improvements based on @erovia's feedback * rework qmk compile and qmk flash to use pathlib * style * Remove the subcommand_name argument from find_keyboard_keymap() Co-authored-by: Erovia <Erovia@users.noreply.github.com>
*	Fix compiling json files	Zach White	2019-12-08	1	-8/+3
\|
*	format code according to conventions [skip ci]	QMK Bot	2019-11-16	1	-1/+3
\|
*	Add CLI command for flashing a keyboard	jorgemanzo	2019-11-15	1	-0/+57
	A new CLI subcommand was added, flash, which behaves very similar to the already present compile CLI comamnd, but with the added ability to target a bootloader. The command is used like so: qmk flash [-h] [-b] [-kb KEYBOARD] [-km KEYMAP] [-bl BOOTLOADER] [filename]. A -kb <keyboard> and -km <keymap> is expected, or a configurator export JSON filename. A bootloader can be specified using -bl <target>, and if left unspecified, the target is assumed to be :flash. -bl can be used to list the available bootloaders. If -km <keymap> is provided, but no -kb <keyboard>, then a message is printed suggesting the user to run qmk list_keyboards.