I got a basic vagrant vm created. I don't have the compile toolchain setup yet. I'm new to building for embedded processors, so I'm still trying to figure out how to build. I installed arm-linux-gnueabi-gcc-4.6 and made a soft link to that from arm-none-eabi-gcc and ran 'STM32F4DISCOVERY=1 RELEASE=1 make' but get loads of warnings. I'm guessing that arm-linux-gnueabi-gcc-4.6 isn't what I should be using?

Anyhow, if you want to see the vm and maybe help get the correct compiler setup...

To setup the vm on your machine:

• install VirtualBox: https://www.virtualbox.org/
  
• install Vagrant: http://www.vagrantup.com/
  
• download the 'build_vm' branch of my fork of the Espruino repo: https://github.com/bluecamel/Espruino/tr­ee/build_vm (I'll send a pull request when this is working)
  
• cd into the vm directory
  
• type 'vagrant up' (this should download the Ubuntu image, then install all of the required packages...it takes several minutes, depending on your bandwidth/machine)
  
• type 'vagrant ssh' (this gives you a ssh session into the machine)
  
• you have access to the Espruino repo within the vm at /Espruino (any files you edit here are synced with your host machine and vice versa)
  
  

For those interested in how I made it (or want to help with or suggest configuration):

It just uses a bare-bones precise32 image that I added a few basic things to (python, pip, git, make, blueprint). I left out arm-linux-gnueabi-gcc-4.6 for now, since I'm not sure that's right.

I used blueprint (http://devstructure.com/blueprint/) to generate the chef config files. Vagrant runs Chef Solo (http://docs.opscode.com/chef_solo.html) using these config files to install all of the packages we need/want in the vm.

If you want to contribute your changes (installed packages and config files):

• type 'blueprint create EspruinoBuild'
  
• type 'blueprint show -C EspruinoBuild'
  
• this should have created a folder named 'EspruinoBuild' in the current directory
  
• replace /espruino/vm/cookbooks/EspruinoBuild with the directory you just created
  
• commit your changes to the repo (all should be config files under the vm directory)
  
• all the rest of us will need to do (after pulling the changes) is type 'vagrant reload' from the vm directory