How to deal with inter-dependencies with jucer projects?

[daniel]

In that case you can treat your library like any other external library. You can add this in the projucer and the exporter will add the linker call to the project file.
There are already very good examples how to achieve this, so I simply quote an arbitrary answer with nice screenshots:

Using system or external libraries in a juce app (libusb, libudev)

This example is for Mac but the same principles apply to other targets. Add the library name to the “External libraries to link” property in the target: [image] In this case I was using curl, the library file is called libcurl.a — so in terms of what you enter into the Projucer strip off “lib” from the the front and remove the file extension. And add the search paths for the headers and the lib in each of the targets configurations (Debug and Release): [image] If some of your files pull …

That approach worked for me using the sodium crypto library…

Or you can use the forum search for “external library” for alternative solutions…

N.B. I also found the solution @adamsky proposed very helpful. The big benefit is, that you can browse the source code and debug much more easily. But as you said, you probably have good reasons to have it as library too.