What is the best Way to Have Two INO files within the same project folder that are unrelated?

I have a project where there will be multiple different versions of the ino file between the different types of hardware supported, but when I compile it I get conflicts between the different versions of the inos. Is there an easy way to segment my .ino files to let my compiler know that they do not need to be compiled together?

There is only one .ino file allowed but you can create as many .cpp files you want.

You can also compiler directives for conditional compiling to “mix” hardware dependent stuff into the same source file.

2 Likes

This topic was automatically closed 182 days after the last reply. New replies are no longer allowed.