Garlicoin Core [GRLC, G]
==========================
What is Garlicoin? – Such coin
Garlicoin is a cryptocurrency like Bitcoin, although it does not use SHA256 as its proof of work (POW). Taking development cues from Tenebrix and Litecoin, Garlicoin currently employs a simplified variant of scrypt.
License – Much license
Garlicoin is released under the terms of the MIT license. See COPYING for more information or see http://opensource.org/licenses/MIT.
Development and contributions – omg developers
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.
Branches
Garlic doesn't grow on branches, so this isn't relevant.
Very Much Frequently Asked Questions
How much garlic can exist? – So many cloves!
Garlic grows from the Earth so it's only limited by the land area.
How to get garlic? – To the moon!
Garlicoin will find you.
Wow plz make garlicoind/garlicoin-cli/garlicoin-qt
The following are developer notes on how to build Garlicoin 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
Translations
Changes to translations, as well as new translations, can be submitted to Bitcoin Core's Transifex page.
Periodically the translations are pulled from Transifex and merged into the git repository. See the translation process for details on how this works.
If the changes are Garlicoin specific, they can be submitted as pull requests against this repository. If it is a general translation, consider submitting it through upstream, as we will pull these changes later on.
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 garlicoins" 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
Garlicoin 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.