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...
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.
© Espruino, powered by microcosm.
Report a problem