Installing MySQL Using a Standard Source Distribution •To unpack a compressed  tar  file,  tar  can uncompress and unpack the distribution if it has  z  option support: If your  tar  does not have  z  option support, use  gunzip  to unpack the distribution and  tar  to unpack it: Alternatively,  CMake  can uncompress and unpack the distribution: Unpacking the distribution file creates a directory named  mysql- VERSION . shell>  gunzip < mysql- VERSION .tar.gz | tar xvf - shell>  tar zxvf mysql- VERSION .tar.gz shell>  cmake -E tar zxvf mysql- VERSION .tar.gz •To unpack a Zip archive, use  WinZip  or another tool that can read  .zip  files. Configure the Distribution Change location into the top-level directory of the unpacked distribution: Build outside of the source tree to keep the tree clean. If the top-level source directory is named  mysql- src  under your current working directory, you can build in a directory named  bld  at the same level. Create the directory and go there: Configure the build directory. The minimum configuration command includes no options to override configuration defaults: The build directory needs not be outside the source tree. For example, you can build in a directory named bld  under the top-level source tree. To do this, starting with  mysql-src  as your current working directory, create the directory  bld  and then go there: shell>  cd mysql- VERSION shell>  mkdir bld shell>  cd bld shell>  cmake ../mysql-src shell>  mkdir bld shell>  cd bld shell>  cmake .. shell>  cmake .. -G "Visual Studio 12 2013" shell>  cmake .. -G "Visual Studio 12 2013 Win64" shell>  cmake .. -G Xcode On macOS, to use the Xcode IDE: On Windows, specify the development environment. For example, the following commands configure MySQL for 32-bit or 64-bit builds, respectively: If you have multiple source trees at the same level (for example, to build multiple versions of MySQL), the second strategy can be advantageous. The first strategy places all build directories at the same level, which requires that you choose a unique name for each. With the second strategy, you can use the same name for the build directory within each source tree. The following instructions assume this second strategy. Configure the build directory. The minimum configuration command includes no options to override configuration defaults: 210