Currently we build Cerbero depencencies for further libraries all at once. Now that guitarix dependencies are in (on aap-guitarix branch) it builds libffi, libz, gnustl, glib, mm-common, libsigc++, and glibmm just for guitarix. It makes everything hard to identify which is really required just for existing mda-lv2 (libsndfile, and inherently ogg, vorbis, and flac).
Cerbero build is however massive and we don't want to have multiple instances/checkouts of it everywhere. At the same time, Cerbero packages have dependencies and each build dependencies may overlap at some stage. Fortunately they don't now, but when we would like to build fluidsynth, glib will be overlapped (as an guitarix dep).
The latest Cerbero has a concept of "package" which might provide help to some solution.
atsushieno
commented
4 years ago
Currently we build Cerbero depencencies for further libraries all at once. Now that guitarix dependencies are in (on
aap-guitarixbranch) it builds libffi, libz, gnustl, glib, mm-common, libsigc++, and glibmm just for guitarix. It makes everything hard to identify which is really required just for existing mda-lv2 (libsndfile, and inherently ogg, vorbis, and flac).Cerbero build is however massive and we don't want to have multiple instances/checkouts of it everywhere. At the same time, Cerbero packages have dependencies and each build dependencies may overlap at some stage. Fortunately they don't now, but when we would like to build fluidsynth, glib will be overlapped (as an guitarix dep).
The latest Cerbero has a concept of "package" which might provide help to some solution.