John Emmas b9bbea7174 It might not be obvious why... but 'ARDOUR::ControlProtocol::name()' needs to be a virtual function ... Basically, libardour is calling functions from libardour_cp and vice versa. For example, libardour needs 'ARDOUR::ControlProtocol::name()' whereas ardour_cp needs 'ARDOUR::Route::soloed()' and various others. Ordinarily, this would require each library to get built before the other one! :-( To get around this (in MSVC at least) one of the libraries must be forced to use late binding (e.g. by declaring its functions as 'virtual'). It looks like this is already being done for most of the other functions from 'ARDOUR::ControlProtocol', so let's do it for this function too...		2017-05-15 14:46:34 +01:00
..
control_protocol	It might not be obvious why... but 'ARDOUR::ControlProtocol::name()' needs to be a virtual function	2017-05-15 14:46:34 +01:00
MSVCardour_cp	Update our MSVC project files to generate the most recent Ardour session file format (ver 5) rather than the older v3 format	2016-08-30 07:15:00 +01:00
basic_ui.cc	Fix set-*-from-edit-range actions, when accessed from control surfaces.	2017-04-01 09:57:06 -05:00
control_protocol.cc	don't actually use a method from libardourcp inside libardour; use a PBD::Signal to avoid linker issues	2017-05-12 17:49:09 +01:00
wscript