mirror of
https://github.com/jwinterm/myriadcoin.git
synced 2026-10-20 06:08:43 +02:00
85 lines
3.3 KiB
Markdown
85 lines
3.3 KiB
Markdown
Myriadcoin Core integration/staging tree
|
|
========================================
|
|
|
|
http://www.myriadcoin.org
|
|
|
|
Copyright (c) 2009-2014 Bitcoin Core Developers
|
|
|
|
Copyright (c) 2014 Myriadcoin Core Developers
|
|
|
|
|
|
What is Myriadcoin?
|
|
-------------------
|
|
|
|
Myriadcoin is an experimental new digital currency that enables instant payments to
|
|
anyone, anywhere in the world. Myriadcoin uses peer-to-peer technology to operate
|
|
with no central authority: managing transactions and issuing money are carried
|
|
out collectively by the network. Myriadcoin Core is the name of open source
|
|
software which enables the use of this currency.
|
|
|
|
For more information, as well as an immediately useable, binary version of
|
|
the Myriadcoin Core software, see http://www.myriadcoin.org/
|
|
|
|
License
|
|
-------
|
|
|
|
Myriadcoin Core is released under the terms of the MIT license. See [COPYING](COPYING) for more
|
|
information or see http://opensource.org/licenses/MIT.
|
|
|
|
Development process
|
|
-------------------
|
|
|
|
Developers work in their own trees, then submit pull requests when they think
|
|
their feature or bug fix is ready.
|
|
|
|
If it is a simple/trivial/non-controversial change, then one of the Myriadcoin
|
|
development team members simply pulls it.
|
|
|
|
If it is a *more complicated or potentially controversial* change, then the patch
|
|
submitter will be asked to start a discussion (if they haven't already) on the
|
|
[mailing list](http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development).
|
|
|
|
The patch will be accepted if there is broad consensus that it is a good thing.
|
|
Developers should expect to rework and resubmit patches if the code doesn't
|
|
match the project's coding conventions (see [doc/coding.md](doc/coding.md)) or are
|
|
controversial.
|
|
|
|
The `master` branch is regularly built and tested, but is not guaranteed to be
|
|
completely stable. [Tags](https://github.com/bitcoin/bitcoin/tags) are created
|
|
regularly to indicate new official, stable release versions of Myriadcoin.
|
|
|
|
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 message 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 bitcoins" 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 -regest mode.
|
|
|
|
**DEBUG_LOCKORDER**
|
|
|
|
Myriadcoin 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 what locks
|
|
are held, and adds warning to the debug.log file if inconsistencies are detected.
|