Phil Hord

Right. On Fri, Aug 26, 2016, 2:35 PM Wurstnase [email protected] wrote: > Thanks, pointers is one thing I need to internalize. Read some of it, and > sometimes I use...

>> Not sure wether Arduino IDE still insists on the folder name, though. >It does. Foldername and ino-name must be the same. Some IDEs use a .pde instead of .ino....

> How should a makefile looks like in that case? Not sure what you mean. Is it this? `SOURCES = $(wildcard *.c) $(wildcard src/avr/*.c) $(wildcard src/arm/*.c)` If we can avoid...

I think you should keep the path structure under BUILDDIR so you do not have filename collisions there. Consider if you have both `src/clock.c` and `src/AVR/clock.c`. Now you find ${BUILDDIR}/clock.o....

Makefiles are tricky things to understand and debug. I made changes to your move_src branch to implement the simple alternative I was suggesting. I think it covers all the cases,...

@wurstnase That's disappointing. Check the compiler flags the IDE generates to see if there's any common folder they can live in, maybe. Or maybe we can rethink the layout.

It's starting to sounds too complicated simply to appease the fickle Arduino IDE. Maybe we should stick with the "-avr.c" scheme.

Interesting. Drawbacks would be that you have to be careful to manage overflow effects. For example, if I have uint8_t fn(uint8_t fp) { static uint8_t remainder; remainder += fp; ......

Good: ./sim --report-temptable|head ; Temperature sensor test -1 ; Sensor 0 0 631.25 1 625.25 2 619.25 3 613.25 4 607.25 5 601.25 6 595.25 7 589.00 Bad: ./sim --report-temptable|head...

This is very interesting. All of the developers on here now do not have a robot arm to command and are unlikely to be able to help with robot-arm specific...