I installed the ATTiny cores
fromhttps://github.com/SpenceKonde/ATTinyCore and all worked well within Arduino 1.6.9 but when I switchd to Visual Micro 1605.12.0 in Visual Studio 2014 I now get build errors for everything even the straightforward Arduino boards and cannot now use VM.
As a test I started a new blank Arduino project in VM and selected Arduinio/Genuino Uno. I also made sure no ATTinys were installed from Board manager and I made the \Documents\Arduino\hardware folder ZZZZhardware to stop its use but when I build I get:
Compiling 'jimstest1' for 'Arduino/Genuino Uno'
Build folder: file:///C:/Users/Jim/AppData/Local/Temp/VMicroBuilds/jimstest1/uno
Summary: Header=1 Prototypes=3 Imports=0
Additional Defines:
Architecture Tools: uino5/bin/
Sketchbook: file:\\\C:\Users\Jim\Documents\Arduino
Sketch Include Paths
Include Path 'C:\Users\Jim\Documents\Arduino\jimstest1'
Core Include Paths
Include Path 'C:\Program Files\Arduino\hardware\arduino\avr\cores\arduino'
Include Path 'C:\Program Files\Arduino\hardware\arduino\avr\variants\standard'
Build Core Paths: C:\Program Files\Arduino\hardware\arduino\avr\cores\arduino
duino5/bin/avr-gcc" -c -g -x assembler-with-cpp -mmcu=atmega328p -DF_CPU=16000000L -DARDUINO=10609 -DARDUINO_AVR_UNO -DARDUINO_ARCH_AVR -I"C:\Program Files\Arduino\hardware\arduino\avr\cores\arduino" -I"C:\Program Files\Arduino\hardware\arduino\avr\variants\standard" "C:\Program Files\Arduino\hardware\arduino\avr\cores\arduino\wiring_pulse.S" -o o"
error*:CreateProcess: No such file or directory
Error compiling core
Obviously the reference to packages\ATTinyCore shouldnt be there.
SpenceKonde, the developer replied:
It sure looks like you have installed a tiny core through board manager? And also, it looks like it's trying to use the default core and the attiny core.
I think this is a visualmicro bug - the Arduino team keeps mucking with the spec for third party hardware packages, so it's entirely possible that they updated it to work with an early 1.6.x version - but the spec has changed in mutually incompatible ways a few times since.. so it wouldn't be surprising if visualmicro was incompatible with it.
I'm not familiar with visualmicro - but if you want to make a new issue to track progress trying to figure out how to make it work with visualmicro, but I can't really put time into getting these sorted out.
Any suggestions