| Bug #90389 | jdbc.cmake does not properly intake the CLI option for MYSQL_CONFIG_EXECUTABLE | ||
|---|---|---|---|
| Submitted: | 11 Apr 2018 17:47 | Modified: | 11 Jun 2018 14:02 |
| Reporter: | Royce Kemp | Email Updates: | |
| Status: | Closed | Impact on me: | |
| Category: | Connector / C++ | Severity: | S3 (Non-critical) |
| Version: | 8.0.7rc | OS: | Any |
| Assigned to: | CPU Architecture: | Any | |
[17 Apr 2018 11:07]
Chiranjeevi Battula
Hello Royce Kemp, Thank you for the bug report. Verified based on internal discussion with dev's. Thanks, Chiranjeevi.
[8 Jun 2018 17:10]
Luis Silva
Posted by developer: MYSQL_CONFIG_EXECUTABLE cmake option added
[11 Jun 2018 14:02]
Paul DuBois
Posted by developer: Fixed in 8.0.12. When configuring to build Connector/C++ with the legacy connector, CMake did not account for the MYSQL_CONFIG_EXECUTABLE option.
Description: When building with the legacy connector, the cmake script jdbc.cmake does not properly intake the CLI option for MYSQL_CONFIG_EXECUTABLE. How to repeat: cmake3 -DMYSQL_CONFIG_EXECUTABLE:FILEPATH=/some/path/bin/mysql_config -DWITH_JDBC=ON . The above command would not use the binary at /some/path/bin/mysql_config but would instead use the system default mysql_config installation (/usr/bin/mysql_config) Suggested fix: Add DMYSQL_CONFIG_EXECUTABLE=${MYSQL_CONFIG_EXECUTABLE} to line 80 of jdbc.cmake