jalr/OpenRGB
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Attempt to work around Windows compile issue

Browse source
This commit is contained in:
Adam Honse 2021-11-07 15:31:45 -06:00
parent c74a9849c0
commit c3e06d732e
1 changed files with 9 additions and 7 deletions
Download patch file Download diff file Expand all files Collapse all files

16
ResourceManager.cpp
View file

@ -1110,17 +1110,19 @@ void ResourceManager::DetectDevicesThreadFunction()
\*-------------------------------------------------*/ \*-------------------------------------------------*/
if(i2c_interface_fail) 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 #ifdef _WIN32
"On Windows, this is usually caused by a failure to load the inpout32 driver.\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" "You must run OpenRGB as administrator at least once to allow inpout32 to set up.\r"
#endif #endif
#ifdef __linux__ #ifdef __linux__
"On Linux, this is usually because the i2c-dev module is not loaded.\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" "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" "This is usually i2c-piix4 for AMD systems and i2c-i801 for Intel systems.\r"
#endif #endif
"See https://help.openrgb.org for additional troubleshooting."); "See https://help.openrgb.org for additional troubleshooting.";
LOG_DIALOG("%s", i2c_message);
} }
} }