libear VS ltools

The BBC did a lot of work in this area (disclaimer: I worked for them), including creating an open source renderer: https://www.bbc.co.uk/rd/blog/2019-08-libear-ebu-audio-renderer-next-generation-open-source. The code is here: https://github.com/ebu/libear. Start at https://github.com/ebu/libear/blob/master/examples/objects_gains.cpp and work back through the code.

My colleague wrote this solution for C++ and cmake:

https://github.com/ebu/libear/commit/40a4000296190c3f91eba79...

This is a cmake function which generates C++ files using no external tools. It's probably not very fast, but if you don't need to handle big files and are already using cmake this is easy to integrate, adds no dependencies and works on all platforms.

https://github.com/jochenleidner/ltools/blob/main/src/bin/bi...

What I found is that many compilers don't like to compile very large source files; so if the binaries you'd like to integrate are big, it might be better to integrate their constituent objects one by one (if applicable).

> I wish binary inclusion was provided by more languages or build systems. For small files it's a very suitable alternative to the difficulties of packaging resources when distributing an application or library.

When it occasionally comes up as a need, I use the bintosrc command available at https://github.com/jochenleidner/ltools