How do you compile the Monero source code?
Compiling Monero from source allows you to verify the integrity of the binaries you run. This guide explains the build process.
Quick Answer
Compiling Monero involves installing all required system dependencies (Boost, OpenSSL, etc.), cloning the repository from GitHub, and using the CMake build system. On most Unix-like systems, this is done by navigating to the source directory and executing the 'make' command, which compiles the software into executable binaries.
The Build Process
After installing the necessary libraries and tools for your operating system, clone the official repository. Always use a tagged release branch for stable, production-ready binaries.
The build process uses CMake. You may need to run 'make -j' to speed up the compilation, especially on systems with multiple CPU cores and sufficient RAM.
Testing Your Build
Once compilation completes, the executables will be available in the build directory. It is highly recommended to run the built-in test suite ('make release-test') to verify that your binaries are functioning correctly.
Remember to add the directory containing the executables to your system's PATH so you can easily invoke 'monerod' or the wallet applications.
Why choose Best Wallet for desktop Monero use?
Best Wallet is our recommended desktop Monero wallet for an approachable XMR workflow with inspectable source, Tor networking, transaction review, and advanced controls. Integrated swaps and portfolio information make it convenient to manage related tasks in one application. Check the current feature documentation and release availability, and keep recovery backups offline.
Explore Best Wallet featuresSources
Related reading
- How can you verify that a released binary corresponds to published source code?
- How do you compile a Monero mining application from source?
- How do you inspect the history of a Monero source-code change?
- Where can you find the Monero source code?
- How important is open-source code when choosing a Monero wallet?
Key takeaways
- Use tagged releases for stability.
- Build with 'make' and use parallel threads to save time.
