You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
litecoin/build_msvc
Wladimir J. van der Laan 3caee16946
Merge #19953: Implement BIP 340-342 validation (Schnorr/taproot/tapscript)
4 years ago
..
bench_bitcoin Added libtest_util library to msvc build configuration. 5 years ago
bitcoin-cli [MSVC] Copy build output to src/ automatically after build 5 years ago
bitcoin-qt Ignore msvc linker warning and update to msvc build instructions. 5 years ago
bitcoin-tx [MSVC] Copy build output to src/ automatically after build 5 years ago
bitcoin-wallet [MSVC] Copy build output to src/ automatically after build 5 years ago
bitcoind [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_cli [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_common [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_crypto [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_qt [gui] PSBT Operations Dialog (sign & broadcast) 4 years ago
libbitcoin_server [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_util Drop unintended bitcoin-tx dependency on libevent 5 years ago
libbitcoin_wallet [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_wallet_tool [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoin_zmq [MSVC] Copy build output to src/ automatically after build 5 years ago
libbitcoinconsensus [MSVC] Copy build output to src/ automatically after build 5 years ago
libleveldb build: Disable msvc warning 4722 for leveldb build 5 years ago
libsecp256k1 Support for Schnorr signatures and integration in SignatureCheckers (BIP 340) 4 years ago
libtest_util Added libtest_util library to msvc build configuration. 5 years ago
libunivalue [MSVC] Copy build output to src/ automatically after build 5 years ago
msbuild/tasks [MSVC]: Create the config.ini as part of bitcoind build 5 years ago
test_bitcoin build: Fix appveyor test_bitcoin build of *.raw 5 years ago
test_bitcoin-qt Ignore msvc linker warning and update to msvc build instructions. 5 years ago
testconsensus scripted-diff: Bump copyright headers 5 years ago
.gitignore Update msvc build to use new vcpkg manifest 4 years ago
README.md Update msvc build to use new vcpkg manifest 4 years ago
bitcoin.sln Included test_bitcoin-qt in msvc build. 5 years ago
bitcoin_config.h [build] msvc: add boost::process 4 years ago
common.init.vcxproj Update msvc build to use new vcpkg manifest 4 years ago
common.qt.init.vcxproj Updated appveyor config: 5 years ago
common.vcxproj [MSVC] Copy build output to src/ automatically after build 5 years ago
libsecp256k1_config.h Update MSVC build config for libsecp256k1 5 years ago
msvc-autogen.py scripted-diff: Add missed copyright headers 5 years ago
vcpkg.json Add sqlite to travis and depends 4 years ago

README.md

Building Bitcoin Core with Visual Studio

Introduction

Solution and project files to build the Bitcoin Core applications msbuild or Visual Studio can be found in the build_msvc directory. The build has been tested with Visual Studio 2017 and 2019.

Building with Visual Studio is an alternative to the Linux based cross-compiler build.

Quick Start

The minimal steps required to build Bitcoin Core with the msbuild toolchain are below. More detailed instructions are contained in the following sections.

cd build_msvc
py -3 msvc-autogen.py
msbuild /m bitcoin.sln /p:Platform=x64 /p:Configuration=Release /t:build

Dependencies

A number of open source libraries are required in order to be able to build Bitcoin Core.

Options for installing the dependencies in a Visual Studio compatible manner are:

  • Use Microsoft's vcpkg to download the source packages and build locally. This is the recommended approach.
  • Download the source code, build each dependency, add the required include paths, link libraries and binary tools to the Visual Studio project files.
  • Use nuget packages with the understanding that any binary files have been compiled by an untrusted third party.

The external dependencies required for building are listed in the build_msvc/vcpkg.json file. The msbuild project files are configured to automatically install the vcpkg dependencies.

Qt

In order to build the Bitcoin Core a static build of Qt is required. The runtime library version (e.g. v141, v142) and platform type (x86 or x64) must also match.

Some prebuilt x64 versions of Qt can be downloaded from here. Please be aware these downloads are NOT officially sanctioned by Bitcoin Core and are provided for developer convenience only. They should NOT be used for builds that will be used in a production environment or with real funds.

To determine which Qt prebuilt version to download open the .appveyor.yml file and note the QT_DOWNLOAD_URL. When extracting the zip file the destination path must be set to C:\. This is due to the way that Qt includes, libraries and tools use internal paths.

To build Bitcoin Core without Qt unload or disable the bitcoin-qt, libbitcoin_qt and test_bitcoin-qt projects.

Building

The instructions below use vcpkg to install the dependencies.

  • Install vcpkg.

  • Use Python to generate *.vcxproj from Makefile

PS >py -3 msvc-autogen.py
  • An optional step is to adjust the settings in the build_msvc directory and the common.init.vcxproj file. This project file contains settings that are common to all projects such as the runtime library version and target Windows SDK version. The Qt directories can also be set.

  • To build from the command line with the Visual Studio 2017 toolchain use:

msbuild /m bitcoin.sln /p:Platform=x64 /p:Configuration=Release /p:PlatformToolset=v141 /t:build
  • To build from the command line with the Visual Studio 2019 toolchain use:
msbuild /m bitcoin.sln /p:Platform=x64 /p:Configuration=Release /t:build
  • Alternatively open the build_msvc/bitcoin.sln file in Visual Studio.

AppVeyor

The .appveyor.yml in the root directory is suitable to perform builds on AppVeyor Continuous Integration servers. The simplest way to perform an AppVeyor build is to fork Bitcoin Core and then configure a new AppVeyor Project pointing to the forked repository.

For safety reasons the Bitcoin Core .appveyor.yml file has the artifact options disabled. The build will be performed but no executable files will be available. To enable artifacts on a forked repository uncomment the lines shown below:

    #- 7z a bitcoin-%APPVEYOR_BUILD_VERSION%.zip %APPVEYOR_BUILD_FOLDER%\build_msvc\%platform%\%configuration%\*.exe
    #- path: bitcoin-%APPVEYOR_BUILD_VERSION%.zip