summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortakageRoshi <36808555+takageRoshi@users.noreply.github.com>2018-11-23 09:53:38 -0700
committerGitHub <noreply@github.com>2018-11-23 09:53:38 -0700
commit31f851a1577b82aaff6519d43ebad0043ab4afde (patch)
tree18d03f594e8f0d3eb0111ec99f4367d1ad2e30ff
parent0b819937fa8163926fab98f8948b1f0207588eb0 (diff)
downloadlaunchpad-polymaker-31f851a1577b82aaff6519d43ebad0043ab4afde.tar.gz
launchpad-polymaker-31f851a1577b82aaff6519d43ebad0043ab4afde.zip
updated readme
removed this : "It appears that VirtualBox does not yet work on Windows 10."
-rw-r--r--README.md2
1 files changed, 0 insertions, 2 deletions
diff --git a/README.md b/README.md
index b1c6b60..3943a52 100644
--- a/README.md
+++ b/README.md
@@ -148,8 +148,6 @@ If you only want to build using the command line, you might want to run your Vag
148 148
149If prefer, you can install the gcc-arm toolchain on your local machine, or you might already have it. You can find all you need [here](http://gnuarmeclipse.livius.net/). 149If prefer, you can install the gcc-arm toolchain on your local machine, or you might already have it. You can find all you need [here](http://gnuarmeclipse.livius.net/).
150 150
151It appears that VirtualBox does not yet work on Windows 10.
152
153If your connection drops out while updating the Vagrant box, you can get stuck, unable to `vagrant up`. To resolve, you need to delete the temp file - `~/vagrant.d/tmp`. 151If your connection drops out while updating the Vagrant box, you can get stuck, unable to `vagrant up`. To resolve, you need to delete the temp file - `~/vagrant.d/tmp`.
154 152
155# Firmware development tips 153# Firmware development tips