I’ve noticed differences between both the cloud compiler and the Particle Dev compiler, the most significant of these being that I don’t get compile errors thrown with Particle Dev, while they are properly thrown in the cloud, even when there are clear issues with the code (like missing semicolons). I also have an issue with Particle Dev where any firmware I try to build for a product always kicks back an error when trying to upload to the Particle Dashboard (it claims that the product versions don’t match even when they do). Is there a good way to get the local copy of the current cloud compiler?
I’ve also noticed when downloading firmware binaries that they can be very different in size (6k vs 76k) for almost exactly the same code. The smaller firmware versions allow my product devices to update correctly, however, the bigger ones fail in flashing every time. After reading a few posts on maximum allowable firmware size I’m convinced that the issue is the size difference. I’d suspect that this is the difference between a firmware update and full code for my product, can anyone confirm?
Finally, I’ve tried to include several libraries in the Web IDE with #include statements, but the compiler says that no such library exists unless I specifically add it to the project by going to the library and clicking “Include in App”. Is there a way to get the cloud compiler to recognize that it has the library with just the #include statements instead of manually having to add each library?
I am using “Latest” on the Web IDE. The compiler in cloud option on Particle Dev is now giving me the opposite problem. Instead of throwing no errors. It’s throwing errors where there aren’t any (See screenshot below. The two errors claim there is a missing constructor in the loop function, but I’m pretty sure the code is good.)
compiler