• Home
  • History
  • Annotate
Name Date Size #Lines LOC

..03-May-2022-

gitian-building/H03-May-2022-

release-notes/H31-Jul-2018-7,3045,862

DoxyfileH A D31-Jul-201872.9 KiB1,7531,274

README.mdH A D31-Jul-20183.5 KiB7859

README_osx.mdH A D31-Jul-20184.6 KiB8366

REST-interface.mdH A D31-Jul-20183.6 KiB9775

assets-attribution.mdH A D31-Jul-2018145 21

benchmarking.mdH A D31-Jul-20181.2 KiB3126

bips.mdH A D31-Jul-20188.1 KiB3533

build-openbsd.mdH A D31-Jul-20187 KiB175128

build-osx.mdH A D31-Jul-20183.1 KiB9662

build-unix.mdH A D31-Jul-201811.2 KiB312213

build-windows.mdH A D31-Jul-20181.3 KiB4329

developer-notes.mdH A D31-Jul-201814.9 KiB431311

dnsseed-policy.mdH A D31-Jul-20182.4 KiB5541

files.mdH A D31-Jul-20181.8 KiB3126

gitian-building.mdH A D31-Jul-201818.5 KiB478340

init.mdH A D31-Jul-20185.1 KiB12688

multiwallet-qt.mdH A D31-Jul-20182.9 KiB4935

reduce-traffic.mdH A D31-Jul-20181.5 KiB3826

release-notes.mdH A D31-Jul-20187.9 KiB179145

release-process.mdH A D31-Jul-201811.4 KiB278198

shared-libraries.mdH A D31-Jul-20183.1 KiB5037

tor.mdH A D31-Jul-20185.6 KiB11683

translation_process.mdH A D31-Jul-20186.3 KiB11278

translation_strings_policy.mdH A D31-Jul-20184.5 KiB11067

unit-tests.mdH A D31-Jul-2018695 1912

zmq.mdH A D31-Jul-20184.3 KiB10779

README.md

1Bitcoin Core 0.13.2
2=====================
3
4Setup
5---------------------
6[Bitcoin Core](http://bitcoin.org/en/download) is the original Bitcoin client and it builds the backbone of the network. However, it downloads and stores the entire history of Bitcoin transactions (which is currently several GBs); depending on the speed of your computer and network connection, the synchronization process can take anywhere from a few hours to a day or more.
7
8Running
9---------------------
10The following are some helpful notes on how to run Bitcoin on your native platform.
11
12### Unix
13
14Unpack the files into a directory and run:
15
16- `bin/bitcoin-qt` (GUI) or
17- `bin/bitcoind` (headless)
18
19### Windows
20
21Unpack the files into a directory, and then run bitcoin-qt.exe.
22
23### OS X
24
25Drag Bitcoin-Core to your applications folder, and then run Bitcoin-Core.
26
27### Need Help?
28
29* See the documentation at the [Bitcoin Wiki](https://en.bitcoin.it/wiki/Main_Page)
30for help and more information.
31* Ask for help on [#bitcoin](http://webchat.freenode.net?channels=bitcoin) on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net?channels=bitcoin).
32* Ask for help on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Technical Support board](https://bitcointalk.org/index.php?board=4.0).
33
34Building
35---------------------
36The following are developer notes on how to build Bitcoin on your native platform. They are not complete guides, but include notes on the necessary libraries, compile flags, etc.
37
38- [OS X Build Notes](build-osx.md)
39- [Unix Build Notes](build-unix.md)
40- [Windows Build Notes](build-windows.md)
41- [OpenBSD Build Notes](build-openbsd.md)
42- [Gitian Building Guide](gitian-building.md)
43
44Development
45---------------------
46The Bitcoin repo's [root README](/README.md) contains relevant information on the development process and automated testing.
47
48- [Developer Notes](developer-notes.md)
49- [Multiwallet Qt Development](multiwallet-qt.md)
50- [Release Notes](release-notes.md)
51- [Release Process](release-process.md)
52- [Source Code Documentation (External Link)](https://dev.visucore.com/bitcoin/doxygen/)
53- [Translation Process](translation_process.md)
54- [Translation Strings Policy](translation_strings_policy.md)
55- [Unit Tests](unit-tests.md)
56- [Unauthenticated REST Interface](REST-interface.md)
57- [Shared Libraries](shared-libraries.md)
58- [BIPS](bips.md)
59- [Dnsseed Policy](dnsseed-policy.md)
60- [Benchmarking](benchmarking.md)
61
62### Resources
63* Discuss on the [BitcoinTalk](https://bitcointalk.org/) forums, in the [Development & Technical Discussion board](https://bitcointalk.org/index.php?board=6.0).
64* Discuss project-specific development on #bitcoin-core-dev on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=bitcoin-core-dev).
65* Discuss general Bitcoin development on #bitcoin-dev on Freenode. If you don't have an IRC client use [webchat here](http://webchat.freenode.net/?channels=bitcoin-dev).
66
67### Miscellaneous
68- [Assets Attribution](assets-attribution.md)
69- [Files](files.md)
70- [Tor Support](tor.md)
71- [Init Scripts (systemd/upstart/openrc)](init.md)
72
73License
74---------------------
75Distributed under the [MIT software license](http://www.opensource.org/licenses/mit-license.php).
76This product includes software developed by the OpenSSL Project for use in the [OpenSSL Toolkit](https://www.openssl.org/). This product includes
77cryptographic software written by Eric Young ([eay@cryptsoft.com](mailto:eay@cryptsoft.com)), and UPnP software written by Thomas Bernard.
78

README_osx.md

1Deterministic OS X Dmg Notes.
2
3Working OS X DMGs are created in Linux by combining a recent clang,
4the Apple binutils (ld, ar, etc) and DMG authoring tools.
5
6Apple uses clang extensively for development and has upstreamed the necessary
7functionality so that a vanilla clang can take advantage. It supports the use
8of -F, -target, -mmacosx-version-min, and --sysroot, which are all necessary
9when building for OS X.
10
11Apple's version of binutils (called cctools) contains lots of functionality
12missing in the FSF's binutils. In addition to extra linker options for
13frameworks and sysroots, several other tools are needed as well such as
14install_name_tool, lipo, and nmedit. These do not build under linux, so they
15have been patched to do so. The work here was used as a starting point:
16[mingwandroid/toolchain4](https://github.com/mingwandroid/toolchain4).
17
18In order to build a working toolchain, the following source packages are needed
19from Apple: cctools, dyld, and ld64.
20
21These tools inject timestamps by default, which produce non-deterministic
22binaries. The ZERO_AR_DATE environment variable is used to disable that.
23
24This version of cctools has been patched to use the current version of clang's
25headers and its libLTO.so rather than those from llvmgcc, as it was
26originally done in toolchain4.
27
28To complicate things further, all builds must target an Apple SDK. These SDKs
29are free to download, but not redistributable.
30To obtain it, register for a developer account, then download the [Xcode 7.3.1 dmg](https://developer.apple.com/devcenter/download.action?path=/Developer_Tools/Xcode_7.3.1/Xcode_7.3.1.dmg).
31
32This file is several gigabytes in size, but only a single directory inside is
33needed:
34```
35Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.11.sdk
36```
37
38Unfortunately, the usual linux tools (7zip, hpmount, loopback mount) are incapable of opening this file.
39To create a tarball suitable for Gitian input, mount the dmg in OS X, then create it with:
40```
41  $ tar -C /Volumes/Xcode/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/ -czf MacOSX10.11.sdk.tar.gz MacOSX10.11.sdk
42```
43
44The Gitian descriptors build 2 sets of files: Linux tools, then Apple binaries
45which are created using these tools. The build process has been designed to
46avoid including the SDK's files in Gitian's outputs. All interim tarballs are
47fully deterministic and may be freely redistributed.
48
49genisoimage is used to create the initial DMG. It is not deterministic as-is,
50so it has been patched. A system genisoimage will work fine, but it will not
51be deterministic because the file-order will change between invocations.
52The patch can be seen here:  [theuni/osx-cross-depends](https://raw.githubusercontent.com/theuni/osx-cross-depends/master/patches/cdrtools/genisoimage.diff).
53No effort was made to fix this cleanly, so it likely leaks memory badly. But
54it's only used for a single invocation, so that's no real concern.
55
56genisoimage cannot compress DMGs, so afterwards, the 'dmg' tool from the
57libdmg-hfsplus project is used to compress it. There are several bugs in this
58tool and its maintainer has seemingly abandoned the project. It has been forked
59and is available (with fixes) here: [theuni/libdmg-hfsplus](https://github.com/theuni/libdmg-hfsplus).
60
61The 'dmg' tool has the ability to create DMGs from scratch as well, but this
62functionality is broken. Only the compression feature is currently used.
63Ideally, the creation could be fixed and genisoimage would no longer be necessary.
64
65Background images and other features can be added to DMG files by inserting a
66.DS_Store before creation. This is generated by the script
67contrib/macdeploy/custom_dsstore.py.
68
69As of OS X Mavericks (10.9), using an Apple-blessed key to sign binaries is a
70requirement in order to satisfy the new Gatekeeper requirements. Because this
71private key cannot be shared, we'll have to be a bit creative in order for the
72build process to remain somewhat deterministic. Here's how it works:
73
74- Builders use Gitian to create an unsigned release. This outputs an unsigned
75  dmg which users may choose to bless and run. It also outputs an unsigned app
76  structure in the form of a tarball, which also contains all of the tools
77  that have been previously (deterministically) built in order to create a
78  final dmg.
79- The Apple keyholder uses this unsigned app to create a detached signature,
80  using the script that is also included there. Detached signatures are available from this [repository](https://github.com/bitcoin-core/bitcoin-detached-sigs).
81- Builders feed the unsigned app + detached signature back into Gitian. It
82  uses the pre-built tools to recombine the pieces into a deterministic dmg.
83