giuliomoro yeah, ability to add a per project make step would be useful and/or 'site settings'
of course, as such I could probably make libbelafull in my own projects too.
one thing that crossed my mind this morning, is that perhaps what I could do on my projects is, copy the libbelafull and bela headers into my own projects (kind of like a sub project) - given there is then no runtime dependancy (except sys libs) that project would then compile regardless of what version the bela software was on.
... so i reduce my dependancy on the 'state' of the bela board, in turn this means I can just release a binary.
imho, reducing dependancies on other projects is always a good thing...
of course, then at 'leisure', i can update that projects copy of the bela headers/libs as required e.g. if the patch is requiring new features.
with cross-compilation, Ive been quite happily running binaries outside of the bela ide/makefile system, so should work well.
the only 'issue' I've encountered (and had to adapt xcBela appropriately), is that if you want to use P5 JS, then there is a dependancy that it has to be in ~/Bela/projects/projectname - otherwise sketch.js does not work. (iirc, a path dependancy?)
oh... and another small oddity /bug(?) with P5 JS...
for some reason it doesn't work if you don't included any command line parameters...it doesn't seem to matter what parameter you use, but it needs at least one ... I usually just tag -X 0 on the end
(non p5 js patches work fine with no parameters sent)