Now, IMHO, I'm not a big fan of the new library specification, as the files of a single library are going to be split among different folders.See the example provided for Servo: Servo.h goes under Servo/src/ but Servo.cpp is under Servo/arch/avr/. This means parsing the directories in search for all the files and thus makes the makefiles more complex.What do you think?
I'd appreciate some feedback from the Arduino team.
Duplicate code for each platform will very likely lead to libraries that poorly support the less-used platforms.
Arduino needs to move closer to C++, rather than try and hide it behind the scenes. All it does for newbies is add to the confusion as they do not realise they are using C++, and parts of the standard are not applicable because of Arduino's hidden background changes and inconsistent use of file structures.
My only concerns is the header is on one folder while the code is on another.Not easy to deal with using plain makefile!
@avenue33Quote from: avenue33 on Sep 09, 2013, 01:08 pmMy only concerns is the header is on one folder while the code is on another.Not easy to deal with using plain makefile!why not?
#ifdef ARDUINO_ARCH_AVR#include ../arch/avr/Servo.cpp#elif ARDUINO_ARCH_SAM#include ../arch/avr/Servo.cpp#else#error The hardware is not supported#endif
Please enter a valid email to subscribe
We need to confirm your email address.
To complete the subscription, please click the link in the
email we just sent you.
Thank you for subscribing!
via Egeo 16