summaryrefslogtreecommitdiff
path: root/Build-Environment-Setup.md
diff options
context:
space:
mode:
authoragaric <agaric@protonmail.com>2017-03-25 16:22:08 +0900
committeragaric <agaric@protonmail.com>2017-03-25 16:22:08 +0900
commit2407b27243896c3a3f5e5ae03600b71ea0e8347e (patch)
tree92dfa90ff491bd4f936fb4d5a772693eea19f61d /Build-Environment-Setup.md
parent76b9a2662a75d65a47fe4ba6cb24bcad2c6acfb6 (diff)
fix link for VAGRANT_GUIDE file
Diffstat (limited to 'Build-Environment-Setup.md')
-rw-r--r--Build-Environment-Setup.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/Build-Environment-Setup.md b/Build-Environment-Setup.md
index 5f8086554b..e8e3cd4685 100644
--- a/Build-Environment-Setup.md
+++ b/Build-Environment-Setup.md
@@ -103,7 +103,7 @@ docker run -e keymap=default -e subproject=ez -e keyboard=ergobox --rm -v D:/Use
This will compile the targeted keyboard/keymap and leave it in your QMK directory for you to flash.
### Vagrant
-If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](doc/VAGRANT_GUIDE.md).
+If you have any problems building the firmware, you can try using a tool called Vagrant. It will set up a virtual computer with a known configuration that's ready-to-go for firmware building. OLKB does NOT host the files for this virtual computer. Details on how to set up Vagrant are in the [VAGRANT_GUIDE file](../../blob/master/doc/VAGRANT_GUIDE.md).
## Verify Your Installation
1. If you haven't already, obtain this repository ([https://github.com/qmk/qmk_firmware](https://github.com/qmk/qmk_firmware)). You can either download it as a zip file and extract it, or clone it using the command line tool git or the Github Desktop application.