giuliomoro I have a branch where you can even compile files in subfolders as part of a C++ project. Maybe this will become useful to you, as you seem to have fairly complex project structures.
hmm, that might be interesting to use....
yeah, my projects are not that complicated... the main thing is that I modularise my software into different libraries.
so bela patches tend to be using a number of different libraries.... and whilst I could copy these (binaries/headers) into the bela projects this is very inconvenient when doing development.
what Ive done to date is something like :
checkout all my GitHub projects into a project directory
then hard link the specific bela projects into bela
~/Bela/projects/soundplane -> ~/projects/BelaPatches/salt/c++/soundplane
the only 'pain' in this is it mean my bela project file needs to link to something like
so what Ive recently been doing a hard link into Bela
~/Bela/external/soundplanelib -> projects/SoundplaneLib/build/release/lib
so I can link using ../external/soundplanelib , which is a little more neutral.
I dont really want to have these as a subdirectories for a couple of reasons
a) there are lots of file
b) they need a makefile to compile, they cannot just be compiled in
what I was hoping is that "Libraries" would be a bit more self contained...
in particular, would use a makefile to compile if they were present...and to allow libs to be linked, rather than directly compile C++ files.
that said, Im sure I can make it work... just need to alter my makefiles to perhaps 'release' to the Library directory.
at the end of the day its just a different way of working... partly because my code is cross-platform, its not just for bela - so I cannot 'conform' to doing it solely the 'bela way'