Currently I developed my code locally. I use the application.cpp file and I’ve created a lot of other .h and .cpp files which I compile with the ARM GGC and the DFU Bootloader on OSX (I set everything up based on this tutorial.
Right now I’d like to start to deploy my code on 5 devices over WiFi/Cloud. I get confused about all the options. I’m wondering if I need to add my code directly as a product, or if I can Flash my code to each of the 5 devices separately as well?
I prefer to use the Desktop IDE or the Particle CLI
My first try was to use the Particle command line interface. I tried to run particle compile photon application.cpp but it kind find my included .h files (my code compiles perfectly with Make).
I don’t know if I need the CLI to compile my code? Or if I just can use the binary which is compile it with ARM GGC?
What would be a recommend directory structure for included files. Is it advisable to make a kind of private library? To library structure changed lately, so I’m a bit confused what is the best road to take.
This feels a bit like a noob question to me. So maybe the answers are just in front of me and I didn’t look good enough.
@nrobinson2000 Thanks for making me aware of this tool. I came across your tool when I started about a year ago with Particle, but it seems better documented right now. I’ll check it out for sure. I like how the bin file is in the directory structure.
I suppose I have to make a choice though, because each method seems to have its own directory structure.
By the way I think in your documentation you should update the #include "application.h" to the currently used #include Particle.h ?