The CMake configuration makes noise about a missing LIBMYSQLPP, but seems OK without it. If the relevant package (mysql++-devel) is installed, CMake correctly detects it, but then disables the SQL functionality anyway. Apparently the SQL support isn't ready. Should we finish it or drop it?
Regardless, if the mysql++-devel package is installed, the database module will be compiled, even if "disabled". This is not only counter-intuitive, but can be a bit of a show-stopper: mysql++.h from the RHEL7 package does not work with more modern compilers (e.g. gcc-12 or 13), which may be needed for the latest ROOT versions, causing the build to fail. So in that case, the only way to turn the database feature off is to uninstall the mysql++-devel package? This should be fixed in CMake.
The CMake configuration makes noise about a missing LIBMYSQLPP, but seems OK without it. If the relevant package (
mysql++-devel
) is installed, CMake correctly detects it, but then disables the SQL functionality anyway. Apparently the SQL support isn't ready. Should we finish it or drop it?Regardless, if the
mysql++-devel
package is installed, the database module will be compiled, even if "disabled". This is not only counter-intuitive, but can be a bit of a show-stopper:mysql++.h
from the RHEL7 package does not work with more modern compilers (e.g. gcc-12 or 13), which may be needed for the latest ROOT versions, causing the build to fail. So in that case, the only way to turn the database feature off is to uninstall the mysql++-devel package? This should be fixed in CMake.