ardour/livetrax
13
0
Fork 0
Code

It might not be obvious why... but 'ARDOUR::ControlProtocol::name()' needs to be a virtual function

Browse Source 
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...
This commit is contained in:
John Emmas 2017-05-15 14:46:34 +01:00
parent 0e4ddcf506
commit b9bbea7174
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
libs/surfaces/control_protocol/control_protocol/control_protocol.h
View File

@ -47,7 +47,7 @@ class LIBCONTROLCP_API ControlProtocol : public PBD::Stateful, public PBD::Scope
ControlProtocol (Session&, std::string name);
virtual ~ControlProtocol();
std::string name() const { return _name; }
virtual std::string name() const { return _name; }
virtual int set_active (bool yn);
bool active() const { return _active; }