mirror of
https://github.com/oxen-io/oxen-core.git
synced 2023-12-14 02:22:56 +01:00
Oxen core repository, containing oxend and oxen cli wallets
7259f07a20
The previous implementation was almost certainly a typo. full_block_size is the maximum index in the encoded_block_sizes array, and size is used as an index in this array. So now 1 <= size <= full_block_size == 8 instead of 1 <= size <= sizeof(full_block_size) == size_of(size_t) == ? (maybe 4 on 32-bit systems!) |
||
|---|---|---|
| contrib/epee | ||
| external | ||
| include | ||
| src | ||
| tests | ||
| utils | ||
| .gitattributes | ||
| .gitignore | ||
| CMakeLists.txt | ||
| Doxyfile | ||
| Makefile | ||
| README | ||
| ReleaseNotes.txt | ||
-= Building CryptoNote =-
On *nix:
Dependencies: GCC 4.7.3 or later, CMake 2.8.6 or later, and Boost 1.53 or later (except 1.54, more details here: http://goo.gl/RrCFmA).
You may download them from:
http://gcc.gnu.org/
http://www.cmake.org/
http://www.boost.org/
Alternatively, it may be possible to install them using a package manager.
To build, change to a directory where this file is located, and run `make'. The resulting executables can be found in build/release/src.
Advanced options:
Parallel build: run `make -j<number of threads>' instead of `make'.
Debug build: run `make build-debug'.
Test suite: run `make test-release' to run tests in addition to building. Running `make test-debug' will do the same to the debug version.
Building with Clang: it may be possible to use Clang instead of GCC, but this may not work everywhere. To build, run `export CC=clang CXX=clang++' before running `make'.
On Windows:
Dependencies: MSVC 2012 or later, CMake 2.8.6 or later, and Boost 1.53 or later. You may download them from:
http://www.microsoft.com/
http://www.cmake.org/
http://www.boost.org/
To build, change to a directory where this file is located, and run this commands:
mkdir build
cd build
cmake -G "Visual Studio 11 Win64" ..
And then do Build.
Good luck!
Build documentation (Doxygen) :
Pequired Packages:
* doxygen
* graphviz (optional)
From root code directory, execute :
doxygen Doxyfile
If you have installed *graphviz*, you can also generate in-doc diagrams :
HAVE_DOT=YES doxygen Doxyfile
The output will go in **doc/html/**