Max_ 1) Where is the "Make parameters" box?
open the side tab of the IDE and go to the settings tab (the usual gear symbol), scroll down there and you'll find make parameters.
Max_ 2) What's the best practice on where to store the library? /root/Bela/libraries ? /usr/lib ?
Probably /usr/local/lib (that's where user-installed (i.e.: not installed by apt-get/dpkg) stuff should go, but as it's a static library, anywhere will do, as long as you specify the full path at link time. E.g.:
LDLIBS=/path/to/static/library/libmyname.a
(note that this effectively adds this file to the list of files that are linked in). If you place it in /usr/local/lib you have the additional advantage of being able to specify it simply with LDLIBS=-lmyname.
3) Where is the makefile of my project which is executed by pressing the IDE's "Build & run" button?
It's /root/Bela/Makefile , which gets called with something like
make -C /root/Bela PROJECT=projectName CL="<list of command line options from the IDE>" <list of make parameters from the IDE, tokenized at the `;` and properly quoted> all runide
Notes: LDFLAGS is not the right place to add static libraries, you should use LDLIBS instead. See the relevant line:
$(CXX) $(BELA_LDFLAGS) $(LDFLAGS) -shared -Wl,-soname,$(LIB_EXTRA_SO) -o lib/$(LIB_EXTRA_SO) $(LIB_EXTRA_OBJS) $(LDLIBS) $(BELA_CORE_LDLIBS) $(BELA_EXTRA_LDLIBS)
make help would tell you:
LDFLAGS= -- linker flags (e.g.: -L. )
LDLIBS= -- libs to link in (e.g.: -lm )
The -L flag to the linker (which you were using above) tells it what folders to search libraries in at link time, whereas -l tells it which libraries to look for (using the usual library mangling that a file called libmyname.{so,a} will be searched when you specify -lmyname. As an alternative to the -l notation you can specify a full path to a .so or .a file, or any other files that would make sense to the linker.
