eried:
pico:
When I move the installation to another directory (\Arduino) the IDE complained it couldn't find avr-g++ (even though the path it showed was in fact correct after moving the directory). I assume there is some registry value that is causing issues?
How are you moving the installation? You need to uninstall it and then install it in another path (or manually change the PATH environment variable)
I was just cutting and pasting the top level directory from \program files\arduino to \arduino
OK, I've changed the PATH variable in environment settings.
How about specifying a path to user libraries? Is this already possible with your library manager?
eried:
pico:
I copied the "tiny" subdir into the "\program files\arduino\arduino ERW 1.0.2\hardware" subdir, but no go... they didn't show up in the boards list at the next restart.
You need to edit boards.txt (try to backup the old one because it contains the "ram" size, and that's not a default thing)
Don't need to do this step with the "official" IDE -- what's the specific changed feature that requires this?
Will the build step correctly find the hardware\tiny\bootloaders and hardware\tiny\cores subdirectories if I simply add hardware\tiny\boards.txt to hardware\arduino\boards.txt?
Edit: Actually, copying the "tiny" directory into "hardware" DOES work, without having to modify anything else, now that I've moved things around out of \program files\arduino. Maybe I had copied the "tiny" directory into the wrong place before, I may have been getting confused as to where things were...
This all seems to be working well. This is very good, now I think I keep just two copies of the IDE on disk, the 0023 version for all my pre-1.0 stuff that I don't want to bring over to 1.0.x for whatever reason, and your EWR 1.0.2 for all the newer stuff. (Actually, there is a third version of the IDE installed, which is for the Teensy 3, but that's based on 1.0.2 so that may be able to be merged as well, but I haven't looked into that yet...)
But the 0023 and the EWR 1.0.2 won't clobber each other every time they are run, which is great! Almost a sane set-up! Another Pepsi is on the way! (BTW, did you look at the feasibility of the "no automatic prototype generation" option for the IDE preprocessor? What do you think?)
eried:
BTW, did the jrlp's suggestion worked for the protocol issue?
I don't know, I had already solved it by copying over a later version of avrdude that had the "wiring" programmer definition in avrdude.conf file.
I would fully expect it work, however, since up until recently stk500v2 was the correct protocol for the mega2560, I believe... so if it worked before why wouldn't it work now? Unless they have changed something with the new mega2560 bootloader (but that would only affect those who had updated their bootloader, and I haven't read that anywhere.)
So I don't know what the story is with the new "wiring" protocol.
Which version of avrdude is your distribution? The one I used to replace is v5.12.