From 91b0ebf38b243de1978f7662b1ecbb0ad3b1b82f Mon Sep 17 00:00:00 2001 From: Robbert van der Helm Date: Thu, 21 May 2020 17:15:24 +0200 Subject: [PATCH] Remove mention of plugin groups flag Since there's no reason for this to be behind a flag. --- src/plugin/configuration.cpp | 1 - src/plugin/plugin-bridge.cpp | 1 - 2 files changed, 2 deletions(-) diff --git a/src/plugin/configuration.cpp b/src/plugin/configuration.cpp index a45944af..a7fd2984 100644 --- a/src/plugin/configuration.cpp +++ b/src/plugin/configuration.cpp @@ -67,6 +67,5 @@ Configuration Configuration::load_for(const fs::path& yabridge_path) { return Configuration(); } - // TODO: Disable plugin groups when not compiling with plugin group support return Configuration(config_file.value(), yabridge_path); } diff --git a/src/plugin/plugin-bridge.cpp b/src/plugin/plugin-bridge.cpp index 25414b29..377c46eb 100644 --- a/src/plugin/plugin-bridge.cpp +++ b/src/plugin/plugin-bridge.cpp @@ -676,7 +676,6 @@ void PluginBridge::log_init_message() { // Include a list of enabled compile-tiem features, mostly to make debug // logs more useful - // TODO: Add a feature flag for the plugin group support init_msg << "Enabled features:" << std::endl; #ifdef USE_BITBRIDGE init_msg << "- bitbridge support" << std::endl;