You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I would like to see a rather different approach. Rather than a single executable from multiple .ino files, create a separate executable from each .ino file. That way a library can have an examples directory with multiple examples in it without having to introduce another layer of directories.
examples/example_A.ino
examples/example_B.ino
...
Alternatively provide a way to specify which .ino files (or .cpp) should be used to generate which executable.
The Arduino Makefile does not support multiple ino
files (sudar/Arduino-Makefile#49), and I'm
not familiar enough with C/C++ to break things out into separate
c/cpp/header files. For now, I'm sticking with this.
Signed-off-by: Hugh Brown (Saint Aardvark the Carpeted) <aardvark@saintaardvarkthecarpeted.com>
After c64f38a we can't compile if we had multiple .ino or .pde files. (The support for multiple files was anyways broken before #39 )
One approach is to concatenate all files together into one big .cpp file and compile that. Arduino IDE does this together with some more preprocessing at https://github.com/arduino/Arduino/blob/master/app/src/processing/app/preproc/PdePreprocessor.java
I am open for other suggestions as well.
The text was updated successfully, but these errors were encountered: