Tim Mayberry b97ab7d7bc Statically link libtimecode into libmidi++ instead of libardour ... 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.		2013-10-20 09:27:35 +10:00
..
macosx
midi++	reverse the visibility.h files assumptions that we don't build shared libs by default	2013-10-18 11:50:44 -04:00
test	Fix compilation with --test.	2013-01-20 18:23:42 +00:00
channel.cc
COPYING
ipmidi_port.cc
libmidi++.pc.in
libmidi++.spec.in
midi.cc
miditrace.cc
midnam_patch.cc	Default to "7bit" controller type if missing, as per DTD.	2013-01-27 17:15:46 +00:00
mmc.cc	Statically link libtimecode into libmidi++ instead of libardour	2013-10-20 09:27:35 +10:00
mmctest.cc
mtc.cc	fixes to get MTC (and probably MIDI clock) slaving working again	2013-08-13 12:53:28 -04:00
parser.cc	major redesign of MIDI port heirarchy and management (part 2)	2013-08-07 22:22:11 -04:00
port.cc	major redesign of MIDI port heirarchy and management (part 2)	2013-08-07 22:22:11 -04:00
run-tests.sh	Fix compilation with --test.	2013-01-20 18:23:42 +00:00
wscript	Statically link libtimecode into libmidi++ instead of libardour	2013-10-20 09:27:35 +10:00