New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bad VagrantFile location in Windows 7 #216
Comments
Thanks for the report, chronzberg, I'll take a look at this. |
Looks like later versions of vagrant are stricter about this. I submitted a patch that fixes it. |
Thanks for the fix. The patch also fixes the same problem on MAC. (And what ever platform Vagrant runs on, I assume.) |
pchickey
pushed a commit
that referenced
this issue
May 2, 2013
I pushed John's patch. Thanks! |
rmackay9
pushed a commit
to rmackay9/rmackay9-ardupilot
that referenced
this issue
May 4, 2013
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In Windows 7 Home Premium, Vagrant v1.2.0, when you run "vagrant up" to create the Vagrant VM, the creation fails on account of the destination mount folder for the ardupilot source not being referenced absolutely. It is referenced as "~/ardupilot". An easy fix is to simply give the absolute path in the Vagrantfile as "/home/vagrant/ardupilot".
The text was updated successfully, but these errors were encountered: