Print the plugin type on initialization

src/wine-host/bridges/group.cpp

@@ -190,7 +190,9 @@ void GroupBridge::accept_requests() {
             // The plugin has to be initiated on the IO context's thread because
             // this has to be done on the same thread that's handling messages,
             // and all window messages have to be handled from the same thread.
-            logger.log("Received request to host '" + request.plugin_path +
+            logger.log("Received request to host " +
+                       plugin_type_to_string(request.plugin_type) +
+                       " plugin at '" + request.plugin_path +
                        "' using socket endpoint base directory '" +
                        request.endpoint_base_dir + "'");
             try {

src/wine-host/individual-host.cpp

@@ -55,6 +55,9 @@ main(int argc, char* argv[]) {
     }
 
     // TODO: Do something with the plugin type
+    // TODO: On the Wine side of things, we should only allow hosting VST3
+    //       plugins when the Meson build option is enabled (because, well,
+    //       otherwise we'd get compile errors)
     const PluginType plugin_type = plugin_type_from_string(argv[1]);
     const std::string plugin_location(argv[2]);
     const std::string socket_endpoint_path(argv[3]);
@@ -64,6 +67,8 @@ main(int argc, char* argv[]) {
               << " (32-bit compatibility mode)"
 #endif
               << std::endl;
+    std::cout << "Preparing to load " << plugin_type_to_string(plugin_type)
+              << " plugin at '" << plugin_location << "'" << std::endl;
 
     // As explained in `Vst2Bridge`, the plugin has to be initialized in the
     // same thread as the one that calls `io_context.run()`. This setup is