Hi, I’ve just got my SparkCore and am not really interested in using the cloud stuff, I want to compile locally.
I’ve managed to edit application.cpp and compile using gcc-arm-none-eabi and flash with dfu-util, and would like to move onto using libraries.
There doesn’t seem to be any documentation regarding where to put libraries. I found the uber-library-example but that doesn’t actually say where to put the libraries. i assume you put it in the core-firmware/inc directory?
Also are people really working within the core-firmware directory and cleaning it out/copying it for every project - there must be a better way than that? I haven’t had a good look yet, but could we not have something similar to Arduino in that you have a libraries directory that’s automagically searched from the Makefile? Or can we do the reverse and put our libraries/sourcecode wherever we want and have it pull in the firmware/comms/common libs?
How do people distribute their projects, they can’t seriously be tarring up the entire core-firmware directory?
On the cloud IDE there appears to be no way to upload libraries although you seem to refer to that ability in various posts - without actually saying how to do it, but hey nice screenshots!
What’s Sparkulator, is that another name for the cloud IDE that’s accessed via the build button? Its certainly not called Sparkulator anywhere on the IDE page itself, maybe the build button should be renamed?
I hate to say it but the documentation is a bit all over the place, some of the links don’t work and the forum/github has some useful information that isn’t included in the docs, like spark-cli, gcc and dfu-util are all relogated to github like they’re second-rate to the cloud stuff. Also its probably worth mentioning somewhere that you must be root or use sudo with dfu-util, like you must use 0.7 or later.
That said I prefer the github layout to the spark website with all those scrolling pages and broken anchor tags that take an age to render. Maybe we should move all of the docs to github then users could edit them and move important stuff hidden in forum posts into somewhere obvious.
From the cloud IDE the docs link doesn’t take me to any documents regarding the IDE, it takes me to getting started plugging in my core - well if I’m using the IDE i’ve pretty much got that far lol!
There really should be a place to go to find out if there is a #define SPARK for example, which seems to be dotted all over various forum posts, but with no solid info. Seems like a pretty basic thing to implement and is essential if you’re going to get any traction porting libraries.
I’d like to know if/how we can do OTA firmware uploads from binaries we’ve compiled using gcc but have no idea where to look for that, spark-cli’s flash facility seems to use USB only.
Oh and that’s another thing, the pretty major point of modes is very well hidden, took me a while to realise you couldn’t just turn on your core and flash it or use the serial monitor, you have to press various buttons in a specific order for a specific time. Hell splash that info all over the homepage please! Funnily enough I can’t even find the link to where that info is anymore…