Author: AbcSxyZ <rossi.sim@outlook.com> Cherry-picked and squashed from:20480d33b
README: change social media position39a209b98
README: Change section orderbdb727981
README: reorganize social medias, split dev specific & and more community related in 2 sectionsbbc6c921c
Add emote to titlese39256825
Install.md : Improve first titleebef882c5
Fix typo1cec6b16b
Extract FAQ and INSTALL into respective files314b6f8e2
Add developement & contribution information directly on readmea7e556924
Remove original block reward schedule8cb73041a
Move licence section at README bottom
3.6 KiB
Building Dogecoin Core
Development is ongoing, and the development team, as well as other volunteers, can freely work in their own trees and submit pull requests when features or bug fixes are ready.
Wow plz make dogecoind/dogecoin-cli/dogecoin-qt
The following are developer notes on how to build Dogecoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
Such ports
- RPC 22555
- P2P 22556
Version strategy
Version numbers are following major.minor.patch
semantics.
Branches
There are 3 types of branches in this repository:
- master: Stable, contains the latest version of the latest major.minor release.
- maintenance: Stable, contains the latest version of previous releases, which are still under active maintenance. Format:
<version>-maint
- development: Unstable, contains new code for planned releases. Format:
<version>-dev
Master and maintenance branches are exclusively mutable by release. Planned releases will always have a development branch and pull requests should be submitted against those. Maintenance branches are there for bug fixes only, please submit new features against the development branch with the highest version.
Contributions ✍️
Developers are strongly encouraged to write unit tests for new code, and to
submit new unit tests for old code. Unit tests can be compiled and run
(assuming they weren't disabled in configure) with: make check
. Further details on running
and extending unit tests can be found in /src/test/README.md.
There are also regression and integration tests of the RPC interface, written
in Python, that are run automatically on the build server.
These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py
Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.
Development tips and tricks
compiling for debugging
Run configure
with the --enable-debug
option, then make
. Or run configure
with
CXXFLAGS="-g -ggdb -O0"
or whatever debug flags you need.
debug.log
If the code is behaving strangely, take a look in the debug.log file in the data directory; error and debugging messages are written there.
The -debug=...
command-line option controls debugging; running with just -debug
will turn
on all categories (and give you a very large debug.log file).
The Qt code routes qDebug()
output to debug.log under category "qt": run with -debug=qt
to see it.
testnet and regtest modes
Run with the -testnet
option to run with "play dogecoins" on the test network, if you
are testing multi-machine code that needs to operate across the internet.
If you are testing something that can run on one machine, run with the -regtest
option.
In regression test mode, blocks can be created on-demand; see qa/rpc-tests/ for tests
that run in -regtest
mode.
DEBUG_LOCKORDER
Dogecoin Core is a multithreaded application, and deadlocks or other multithreading bugs
can be very difficult to track down. Compiling with -DDEBUG_LOCKORDER
(configure CXXFLAGS="-DDEBUG_LOCKORDER -g"
) inserts run-time checks to keep track of which locks
are held, and adds warnings to the debug.log file if inconsistencies are detected.