< Dev | Build Documentation | monero-gui
The build process of building any of the packages by Whonix developers is always very similar. This very wiki page explain how to build package
monero-gui. By replacing the name of the package monero-gui with the name of any other package you might be interested in building, the other package would be build. You have two options.
- A) Instructions on this page about how to build the monero-gui package from source code without verifying software signatures for simplicity.
Get Build Dependencies
Update your package lists.
sudo apt-get update
Install from Debian repository.
sudo apt-get install build-essential devscripts git
Change Directory to Build Folder
This chapter is recommended for better usability, but is not strictly required. 
mkdir -p ~/monero-gui-build
Change directory to folder
Get the Source Code
Get the the package's source code.
git clone https://github.com/Whonix/monero-gui.git
Remember it is Whonix, not whonix! If you are prompted for a username for github, it means you have mistyped the web address.
Change Directory to Source Code Folder
Get into the package's source code folder because later on package build commands are expected to be run from the root of the source folder.
This is optional in case you want to build from master branch.
Do not use version
0.1 but a sensible version number.
git checkout 0.1
Build the Package
When a package is build using
dpkg-buildpackage the resulting packages will be created in the parent folder. I.e. in this case in the
Should show something like this.
monero-gui monero-gui0.1-1_amd64.buildinfo monero-gui0.1-1_amd64.changes
sudo dpkg -i ../monero-gui_0.1-1_amd64.deb
Delete temporary files debhelper files in package source folder as well as debhelper artifacts (.deb file etc.) in parent folder.
1) Show extraneous (temporary files debhelper) files.
git clean -ndff
2) NOTE: Read above output carefully if you added files of your own files to that folder.
If that looks good, actually remove.
git clean -dff
3) Delete debhelper artifacts (.deb file etc.) in parent folder.
When a package is build using
dpkg-buildpackagethe resulting packages will be created in the parent folder. It's better for usability if this is not the user's home folder since many other files may already reside there. Thereby making the build result files more difficult to find or delete. This is a missing Debian feature. See: dpkg-buildpackage: support output directory other than .. [archive]
This is a wiki. Want to improve this page? Help is welcome and volunteer contributions are happily considered! Read, understand and agree to Conditions for Contributions to Whonix ™, then Edit! Edits are held for moderation. Policy of Whonix Website and Whonix Chat and Policy On Nonfreedom Software applies.
Copyright (C) 2012 - 2020 ENCRYPTED SUPPORT LP. Whonix ™ is a trademark. Whonix ™ is a licensee [archive] of the Open Invention Network [archive]. Unless otherwise noted, the content of this page is copyrighted and licensed under the same Freedom Software license as Whonix ™ itself. (Why?)