Tim Mayberry
b97ab7d7bc
This is necessary to get the libmidi++ test to work as libmidi++ has unresolved symbols in libtimecode. This was not a problem when libtimecode was statically linked into libardour if the executable depended on both libtimecode and libardour as the symbols would get resolved. This is not true for the midi++ test case as it doesn't depend on libardour Also as libmidi++ only references symbols from one object file in the libtimecode static archive only that object file gets included/exported from libmidi++. This is fixed by adding a dummy reference to a symbol in the other object file in the libtimecode static archive. |
||
|---|---|---|
| .. | ||
| appleutility | ||
| ardour | ||
| audiographer | ||
| backends | ||
| clearlooks-newer | ||
| clearlooks-older | ||
| evoral | ||
| fst | ||
| gtkmm2ext | ||
| libltc | ||
| midi++2 | ||
| panners | ||
| pbd | ||
| qm-dsp | ||
| rubberband | ||
| surfaces | ||
| taglib | ||
| timecode | ||
| vamp-plugins | ||
| vamp-sdk | ||