next topic »

[Reply #15 on:]

In other words, why Arduino IDE does not have an interface similar to avrdude GUI? Considering that one of the goals is to support other AVRs as well, I think is time to have the required tool to upload the .hex files.

Why we need it... Imagine that maybe I'm making boards for others, boards which use different ATmegas and I need to upload hex files to test the board functionality, frequently switching from one ATmega to another (and obviously, from a hex file to another). For those hex files, I need to compile only once. But there can be various scenarios...

For the start, it will be good to have a GUI interface to Optiboot bootloader.
BTW, Optiboot bootloader support ATmega168P which is not yet supported by Arduino IDE and such interface will help if you decided to go beyond Arduino language.

_____________
Edit:
A funny thing: the users of MPIDE wants the same thing!

[Reply #16 on:]

http://www.arduino.cc/playground/Learning/CommandLine

However I suggest to not go for make but for scons.

https://github.com/suapapa/arscons

scons is much easier to pickup and maintain.

[Reply #17 on:]

However I suggest to not go for make but for scons.

https://github.com/suapapa/arscons

scons is much easier to pickup and maintain.

Despite the fact that make is used literally everywhere? And it's as simple as (for my makefile) typing "make" "make upload" or "make monitor" (or "make upload monitor")

[Reply #18 on:]

...less than an hour.

Wow, that's some huge program! 

3ms is less than an hour. Just thought I'd point that out.

I find myself in the same situation as the original poster sometimes: I have to wait for the whole sketch to recompile because I forgot to plug in the board. Is there any way to get the basic Arduino IDE to only compile/link the parts that have changed? This would also be useful for compiling sketches with multiple files: if you haven't changed the file, it doesn't need to recompile.

[Reply #19 on:]

make is used quite often for historic / backwards compatibility reasons. If you start from scratch there is no need to go for make. Make has awkward syntax and little to no debug support. scons on the other hand is based on python. That is instead of tricking your way through complicated stuff you can just code it (and debug it). I find scons ***way*** simpler to pick up than make. I defintely invested more time in scons than in make. For the very reason that make has lots of nasty surprises and scons is simple. For my private projects I will use scons over make 99 out of 100.

[Reply #20 on:]

http://www.arduino.cc/playground/Learning/CommandLine

However I suggest to not go for make but for scons.

https://github.com/suapapa/arscons

scons is much easier to pickup and maintain.

Hi Klein,

Consider also this scenario, from the MPIDE forums:

I would like to send a hex file to a customer and give them the ability to upload without sending the whole project.

. I've posted the link on the previous post. Make is (a solution but) definitely not for them (clients), and is scaring for beginners.
Anyway, is not my problem (even if it is a real one considering all the cases) as I'm successfully using avrdude-GUI with the last version of avrdude. The OP from the MPIDE forums said also:

I wish MPIDE could be used to upload hex files without compiling, that would be easy!

Best regards,
Vasi