From c3e06d732ed58eefc76a08440ceb69eeea22f311 Mon Sep 17 00:00:00 2001 From: Adam Honse Date: Sun, 7 Nov 2021 15:31:45 -0600 Subject: [PATCH] Attempt to work around Windows compile issue --- ResourceManager.cpp | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/ResourceManager.cpp b/ResourceManager.cpp index d45ec267..065fe2fd 100644 --- a/ResourceManager.cpp +++ b/ResourceManager.cpp @@ -1110,17 +1110,19 @@ void ResourceManager::DetectDevicesThreadFunction() \*-------------------------------------------------*/ if(i2c_interface_fail) { - LOG_DIALOG("One or more I2C/SMBus interfaces failed to initialize.\r" + const char* i2c_message = "One or more I2C/SMBus interfaces failed to initialize.\r" #ifdef _WIN32 - "On Windows, this is usually caused by a failure to load the inpout32 driver.\r" - "You must run OpenRGB as administrator at least once to allow inpout32 to set up.\r" + "On Windows, this is usually caused by a failure to load the inpout32 driver.\r" + "You must run OpenRGB as administrator at least once to allow inpout32 to set up.\r" #endif #ifdef __linux__ - "On Linux, this is usually because the i2c-dev module is not loaded.\r" - "You must load the i2c-dev module along with the correct i2c driver for your motherboard.\r" - "This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.\r" + "On Linux, this is usually because the i2c-dev module is not loaded.\r" + "You must load the i2c-dev module along with the correct i2c driver for your motherboard.\r" + "This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.\r" #endif - "See https://help.openrgb.org for additional troubleshooting."); + "See https://help.openrgb.org for additional troubleshooting."; + + LOG_DIALOG("%s", i2c_message); } }