Moderator: igrr
All the libraries are .cpp and .h so what you call your files shouldn't matter much ,but they will probably only run in the Arduino IDE as ino with the setup() and loop() functions in place .
Change a program file from .ino to .cpp and see what you get come up.
You could try changing setup() to main() maybe
tytower wrote:Does it matter what file ending ?
All the libraries are .cpp and .h so what you call your files shouldn't matter much ,but they will probably only run in the Arduino IDE as ino with the setup() and loop() functions in place .
Change a program file from .ino to .cpp and see what you get come up.
You could try changing setup() to main() maybe
The file extension doesn't matter much. But what I don't like about .ino files is that it gets huge and hard to manage when the software grows. Dividing the main software into .cpp and .h pairs like libraries would be much more manageable. It is good software engineering practice. Arduino .ino actually fosters bad practice by encouraging developers to lump everything into a single file. This is why I prefer a C++ IDE like Atmel Studio compared to arduino ide when developing on arduino.
Personally I use the Tabs and stick the functions that can be separated out in their own tab and call and return a value and you can overload them there too.