I assume this is meant for Particle Dev/Particle CLI users, who have been stuck with throwing everything into the same directory.
I looked into the commit assosicated with this enhancement and see that when you have a “src” directory, it then calls this an “extended” application environment; this includes the sibling “lib” directory and subfolders.
Does the .ino go in src/?
How do I #include the libs in lib from within my .ino?
Let’s say I want to use the Blynk library, located at lib/blynk/blynk.h.
Do I include by:
../lib/blynk/blynk.h (relative to the .ino in src)
lib/blynk/blynk.h (relative to the project root)
blynk/blynk.h (like Particle Build, relative to the lib root)
I tried to play around with this since it’s something I’ve been looking forward to for a while, but can’t get any configuration to build within Particle Dev (haven’t tried CLI yet).
I spoke too soon - this arrangement above compiles but produces a completely unusable binary. Am I missing something? Can I use this “feature” before you guys fully release the “Libraries v2” shenanigans?