Installing MySQL Using a Standard Source Distribution When you run  cmake , you might want to add options to the command line. Here are some examples: • -DBUILD_CONFIG=mysql_release : Configure the source with the same build options used by Oracle to produce binary distributions for official MySQL releases. • -DCMAKE_INSTALL_PREFIX= dir_name : Configure the distribution for installation under a particular location. • -DCPACK_MONOLITHIC_INSTALL=1 : Cause  make package  to generate a single installation file rather than multiple files. • -DWITH_DEBUG=1 : Build the distribution with debugging support. For a more extensive list of options, see Section 2.9.7, “MySQL Source-Configuration Options” . To list the configuration options, use one of the following commands: If  CMake  fails, you might need to reconfigure by running it again with different options. If you do reconfigure, take note of the following: To prevent old object files or configuration information from being used, run these commands in the build direcotry on Unix before re-running  CMake : Or, on Windows: Before asking on the MySQL Community Slack, check the files in the  CMakeFiles  directory for useful information about the failure. To file a bug report, please use the instructions in Section 1.6, “How to Report Bugs or Problems” . On Unix: The second command sets  VERBOSE  to show the commands for each compiled source. Use  gmake  instead on systems where you are using GNU  make  and it has been installed as  gmake . On Windows: Build the Distribution shell>  cmake .. -L # overview shell>  cmake .. -LH # overview with help text shell>  cmake .. -LAH # all params with help text shell>  ccmake .. # interactive display shell>  make clean shell>  rm CMakeCache.txt shell>  devenv MySQL.sln /clean shell>  del CMakeCache.txt shell>  make shell>  make VERBOSE=1 shell>  devenv MySQL.sln /build RelWithDebInfo •Each time you run  CMake , you must run  make  again to recompile. However, you may want to remove old object files from previous builds first because they were compiled using different configuration options. •If  CMake  is run after it has previously been run, it may use information that was gathered during its previous invocation. This information is stored in  CMakeCache.txt . When  CMake  starts, it looks for that file and reads its contents if it exists, on the assumption that the information is still correct. That assumption is invalid when you reconfigure. 211