Dash - Reinventing Cryptocurrency
Go to file
JeremyRand 26880c34cd build: Use PACKAGE_TARNAME and new bin names in NSIS script.
Replaces the hardcoded string "bitcoin" with the autoconf variable PACKAGE_TARNAME; fixes #7265.

Places where I chose not to replace:

1. bitcoin.ico wasn't replaced because it doesn't seem to be relevant to the build system and its filename never affects the end user.
2. InstallDir wasn't replaced because the current text has an uppercase B, and I'm not sure of a good way to capitalize the result of PACKAGE_TARNAME.
3. A comment in the Main Installer section wasn't replaced because comments don't ever face the end user.
4. The registry value "URL:Bitcoin" wasn't replaced for the same reason as InstallDir.
5. Startup shortcut wasn't replaced for the same reason as InstallDir.

All other appearances of "bitcoin" were replaced with PACKAGE_TARNAME, except for the bin names, which were instead replaced with the new bin name autoconf variables.
2016-04-11 04:01:23 +00:00
.tx qt: translation update prior to opening 0.12 translations 2015-11-01 16:11:50 +01:00
build-aux/m4 [build-aux] Update Boost & check macros to latest serials 2016-03-19 15:24:00 +08:00
contrib Merge #7776: build: Remove unnecessary executables from gitian release 2016-04-05 15:44:48 +02:00
depends [Depends] Latest config.guess & config.sub 2016-03-18 09:06:08 +08:00
doc Merge #7793: [doxygen] Fix member comments 2016-04-05 17:49:47 +02:00
qa Test relay of version 2 transactions 2016-04-07 14:59:50 -04:00
share build: Use PACKAGE_TARNAME and new bin names in NSIS script. 2016-04-11 04:01:23 +00:00
src Merge #7786: Doc: Update isStandardTx comment 2016-04-09 12:13:21 +02:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore Merge pull request #6813 2015-10-26 09:09:33 +01:00
.travis.yml [travis] Exit early when check-doc.py fails 2016-03-03 13:05:22 +01:00
autogen.sh autogen.sh: warn about needing autoconf if autoreconf is not found 2016-02-13 04:44:42 +08:00
configure.ac build: define base filenames for use elsewhere in the buildsystem 2016-04-11 04:01:23 +00:00
CONTRIBUTING.md Note that reviewers should mention the commit hash of the commits they reviewed. 2015-12-10 22:44:09 -08:00
COPYING Update license year range to 2016 2016-01-17 23:38:11 +05:30
INSTALL Prettify some /Contrib READMEs 2013-10-21 20:07:31 -04:00
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 2015-12-14 02:11:10 +00:00
Makefile.am build: define base filenames for use elsewhere in the buildsystem 2016-04-11 04:01:23 +00:00
README.md Check if zmq is installed in tests, update docs 2016-03-10 15:41:13 -08:00

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental new digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin 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 Bitcoin Core software, see https://bitcoin.org/en/download, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

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

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

The Travis CI system makes sure that every pull request is built for Windows and Linux, OS X, and that unit and sanity tests are automatically run.

Manual Quality Assurance (QA) Testing

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.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.