Yes, written instructions for installing Monero on your system can be found here with a video tutorial including GUI setup and testing here
# update Ubuntu's repository
sudo apt update
#install git to download latest Monero source code from github
sudo apt install git
# install dependencies to be able to compile Monero
sudo apt install ...
GUI daemon manager is recently merged into monero-core. I.e you can start/stop local daemon from GUI. This PR basically means that monerod is getting built when you build the GUI. Unfortunately win32 still requires some manual work.
Got some help from radfish on github...
Here's what radfish said...
You need to manually merge monero-project/monero-core/PR # 14 in order
to build (alternatively use develop branch in this repo), because
monero daemon repo was updated to not build/install wallet lib/headers
by default (need to pass ...
There are instructions in the github repo: https://github.com/monero-project/monero#compiling-monero-from-source
If you get stuck, I suggest asking the specific question to help you move forward, with your OS specified and steps taken so far.
At this time, there are not any compiled alpha GUI binaries.
That being said, when such binaries exist, the only safe places to download said binaries from are:
Github - https://github.com/monero-project/monero/releases
getmonero.org - https://getmonero.org/downloads/
One last possibility is the stickied posts on https://reddit.com/r/monero, but use all ...
It is much harder to compile software for Windows than it is for GNU/Linux or MacOSX. Instructions do exist in one of Ilya Kitaev's GitHub forks, but they haven't been merged yet at time of writing. They are copied (almost verbatim) below:
Install msys2, follow the instructions on that page on how to update packages to the latest ...
You can download the files for the build you would like to examine under the "Steps and Logfiles" section. For Windows, you will often find a .zip file. The file you can download is underlined in red.
Not all builds will have files you can download and run.
Finally, since these are not official releases, they may not be stable or as safe as official ...
There is no such thing yet, but is a a long wanted goal.
Progress along those lines was made in the last few months, with an automated build system based on Travis, maintained by a contributor under the username 'pigeons'.
I do not know of a timeline for future steps towards deterministic builds, though.
Start by opening a terminal and installing all the dependencies:
sudo apt-get install libgtest-dev && cd /usr/src/gtest && sudo cmake . && sudo make && sudo mv libg* /usr/lib/
sudo apt-get install build-essential cmake pkg-config libboost-all-dev libssl-dev libzmq3-dev libunbound-dev libsodium-dev
cd to the directory you ...
The simple answer is that make will build a whole bunch of stuff (i.e., monerod, monero-wallet-cli, monero-wallet-gui, monero-blockchain-import, etc., along with all the files it compiles as precursors to those binaries). At the end of the build process, it builds tests. Your error comes at the stage of the build process where all the main binaries have ...
This is libunwind. It probably was wrongly detected. In the meantime, you should be able to build by removing libunwind-dev (or similar) from your system.
It might also be that you changed your system and cmake kept some cache. A rebuild from scratch (that is, removing all build trees) might fix this, if this is indeed the case.
Sure, assuming you have not made any branches, and that doesn't sound likely, follow these steps:
if you have made any changes to the repo: git stash
git pull --rebase
if you have made any changes to the repo: git stash pop
So in the likely case you haven't changed anything, it's just one step. Then build again (make).
If you did make changes, there's a ...
The MyMonero desktop app is built with Electron. To build it you need to install NodeJS and NPM.
After installing Node, download the source code from GitHub, open command prompt and go to the directory containing the source code, run npm install to grab the dependencies and then npm start to launch the program.
I found out that the problem was in line endings.
On Windows it's defaulted to CRLF of course with core.autocrlf set to true.
If I manually change line endings to Unix-style LF all checks pass okay:
C:\monero\monero-gitian\v0.15.0.1-win\dikdust>gpg --verify monero-win-0.15-build.assert.sig
gpg: assuming signed data in 'monero-win-0.15-build.assert'
Kovri build instructions are on the main Kovri repository here:
This document will always be the most up-to-date location for build information, so I will not go into the process here.
Build instructions are on the main repository's main README.md page:
As this is bound to change, and that location will always be the most up-to-date of anything, I don't feel it's appropriate to walk through the steps here.
The problem being experienced has to do with how the compiler uses libraries.
As noted in the github link provided by Florian, one solution to this problem is simply to uninstall libgtest-dev. This actually didn't work the first time I tried to make. Once I did make clean first, it worked as intended.
Another solution is so comment out the lines of ...
You can't make static monero binaries. The closest you can do is a dynamic build which links statically against most libraries, such as boost, etc.
The Makefile has a number of predefined targets for this, called *static* (because close enough). For example:
You'll still end with a few dynamic libraries, but a lot fewer.
It was the server hosting the binaries that was compromised during this attack. Luckily signed files with the genuine binary hashes were available on other sources and servers, so the attack was noticed fairly quickly. Here is the announcement on r/monero relating to the compromise: https://www.reddit.com/r/Monero/comments/dyfozs/...
More recently there are submodules in the Monero source tree, thus you must git submodule init && git submodule update from the root of a cloned repository.
Then to link statically, make release-static. I'd suggest running make clean first if you have been trying and failing beforehand.
A present date solution that is more compact (installs the submodules and checks out the branch automatically when cloning) is:
sudo apt update && sudo apt install build-essential cmake pkg-config libboost-all-dev libssl-dev libzmq3-dev libunbound-dev libsodium-dev libunwind8-dev liblzma-dev libreadline6-dev libldns-dev libexpat1-dev doxygen ...