Visual Studio build configuration for Bitcoin Core #11526

sipsorcery · 2017-10-19T10:21:33Z

This PR allows Bitcoin Core to be relatively easily built with Visual Studio 2017. It's anticipated that it could be useful for devs familiar with Visual Studio and Microsoft's tooling. In particular the ability to use the VS debugger is a big benefit.

~~Caveats:~~

There are some minor code changes required on Bitcoin Core in order for msvc to be able to successfully compile. I'll submit them in a separate PR, The code changes are available in Minimal code changes to allow msvc compilation #11528 Minimal code changes to allow msvc compilation #11558 and bench: use std::chrono rather than gettimeofday #11562.
~~The vcpkg for SECP256K1 has not yet been accepted by Microsoft. The files are available from this PR and should be copied into a vcpkg/ports/secp256k1 directory prior to vcpkg install steps.~~

Update: For anyone wishing to test out the Visual Studio build with the various open pull requests the steps are:

Clone and build Vcpkg (Microsoft's new open source C/C++ package manager)
- git clone https://github.com/Microsoft/vcpkg
- .\bootstrap-vcpkg.bat
Set up Visual Studio to automatically reference vcpkg installs: .\vcpkg integrate install
Install the required packages (replace x86 with x64 as required):
- vcpkg install boost:x86-windows-static
- vcpkg install libevent:x86-windows-static
- vcpkg install openssl:x86-windows-static
- vcpkg install zeromq:x86-windows-static
- vcpkg install berkeleydb:x86-windows-static
- vcpkg install secp256k1:x86-windows-static
- vcpkg install leveldb:x86-windows-static
git clone https://github.com/bitcoin/bitcoin.git
git checkout -b testbuild
git pull origin pull/11526/head # Visual Studio build configuration for Bitcoin Core
~~git pull origin pull/11558/head # Minimal code changes to allow msvc compilation~~
~~git pull origin pull/11562/head # bench: use std::chrono rather than gettimeofday~~
~~Copy and unzip attached bitcoin-config.h to src/config, edit as required bitcoin-config.zip~~
~~git pull origin pull/13031/head # gmtime fix for msvc~~
Build the Visual Studio solution which, if successful, will result in all but the Qt dependent libraries/programs being built. If the build fails please add a comment.

laanwj · 2017-10-19T12:41:05Z

Concept ACK, this is much-requested.

However IMO to be accepted upstream this needs committed maintenance, not just a one-time drop. Will you maintain this in the future when new files are added? It's bound to break from time to time with build updates (most of us are not able to use this).

sipa · 2017-10-19T12:43:01Z

Also, is there a way to have Travis do an MSVC build? That could make sure that the configuration doesn't bitrot.

laanwj · 2017-10-19T12:49:37Z

Also, is there a way to have Travis do an MSVC build? That could make sure that the configuration doesn't bitrot.

Maybe. I disagree that keeping the MSVC build up to date should be required for merging anything; this would require everyone that changes things to keep MSVC up to date, which most are not able to do because they do not run that platform.

practicalswift · 2017-10-19T13:12:46Z

build_msvc/README.md

+---------------------
+The instructions below use vcpkg to install the dependencies.
+
+- Clone and vcpkg from the [github repository](https://github.com/Microsoft/vcpkg) and install as per the instructions in the main README.md,


Nit: s/,$/./

practicalswift · 2017-10-19T13:13:51Z

build_msvc/README.md

+
+- 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](https://www.nuget.org/) packages with the understanding that any binary files have been compiled by an untrusted third party,
+- Use Microsoft's [vcpkg](https://docs.microsoft.com/en-us/cpp/vcpkg) to download the source packages and build locally. This is the recommended approach.


Nit: Start with the recommended approach.

Nit: s/,$/./ :-)

jonasschnelli · 2017-10-19T18:41:46Z

I'm not sure if we should include this in the main repository. We had similar discussions in #5276 (Xcode project).
AFAIK, those "project files" tend to get outdated very fast. IMO the authors of MSVC and Xcode do not take too much care about backwards compatibility of their file formats...
Also, merging this may lead to someone trying to include a CMake or XCode project.

I'd prefer an external gist/repository and maybe a link to that project (easier to remove if outdated).

meshcollider · 2017-10-20T04:44:22Z

Hmm the whitespace lint checker is going crazy, it might need some modifications because its pretty hard to me to see what its catching here

Edit: there's definitely some tab characters mixed up in there, maybe that's the problem

Edit 2: Nope there's definitely a lot of trailing whitespace too, looks like its working fine, there's just a lot to process. Might want to do a regex find and replace to save yourself doing it manually :)

sipsorcery · 2017-10-20T05:45:15Z

@meshcollider I'm tracking down the lint failure. I've already removed all tabs and trimmed all end of line whitespace with sed. Looks like there's a rule somewhere that requires certain types of files to have end of line as the last character. Will keep digging.

maflcko · 2017-10-20T07:07:26Z

@sipsorcery When saving the file in your editor, choose "Linux encoding" instead of "Windows encoding" for new lines.

sipsorcery · 2017-10-20T07:49:37Z

No '\r|\t' are in the diff patch now so hopefully lint will be happy.

If this PR does go through there will be an issue with the lint rules. In my troubleshooting I've discovered Visual Studio will add tab characters into a solution (.sln) file whenever it's opened. It possibly does the same for it's other .vcproj, .vcxproj.user and .vcxproj.filters files as well although it didn't during my quick testing.

I could add a new rule to contrib/devtools/lint-whitespace.sh for these file types but I think I'll leave it until a decision on this PR is made.

sipsorcery · 2017-10-20T10:00:22Z

@laanwj

However IMO to be accepted upstream this needs committed maintenance, not just a one-time drop. Will you maintain this in the future when new files are added? It's bound to break from time to time with build updates (most of us are not able to use this).

Yes.

If the VS build config gets added I will commit to maintaining it for a minimum of 3 years (end of 2020) excepting death, disability etc. As character assessment I've been an open source contributor since the early noughties: sourceforge, codeplex, bitbucket, github etc; no project highlights that will impress you guys but the relevant point is that I'm capable of hanging around.

I'd also expect the VS config to become popular in a short space of time which would reduce the maintenance burden.

practicalswift · 2017-10-20T13:12:52Z

@sipsorcery

Is there some tool to generate the vcxproj, vcxproj.filters and sln files programmatically from an easy-to-read text format that allows for easy tracking over time?

The very verbose XML build files contain a lot of duplication and random artifacts, so the same data should be possible to represent in a much more compact and human friendly way.

The following files 34 files are quite hard to reason about and/or review in detail due to the large amount of redundancy and general verbosity:

build_msvc/bench_bitcoin/bench_bitcoin.vcxproj
build_msvc/bench_bitcoin/bench_bitcoin.vcxproj.filters
build_msvc/bitcoin-cli/bitcoin-cli.vcxproj
build_msvc/bitcoin-tx/bitcoin-tx.vcxproj
build_msvc/bitcoin-tx/bitcoin-tx.vcxproj.filters
build_msvc/bitcoin.sln
build_msvc/bitcoind/bitcoind.vcxproj
build_msvc/bitcoind/bitcoind.vcxproj.filters
build_msvc/libbitcoin_cli/libbitcoin_cli.vcxproj
build_msvc/libbitcoin_cli/libbitcoin_cli.vcxproj.filters
build_msvc/libbitcoin_common/libbitcoin_common.vcxproj
build_msvc/libbitcoin_common/libbitcoin_common.vcxproj.filters
build_msvc/libbitcoin_crypto/libbitcoin_crypto.vcxproj
build_msvc/libbitcoin_crypto/libbitcoin_crypto.vcxproj.filters
build_msvc/libbitcoin_qt/libbitcoin_qt.vcxproj
build_msvc/libbitcoin_qt/libbitcoin_qt.vcxproj.filters
build_msvc/libbitcoin_server/libbitcoin_server.vcxproj
build_msvc/libbitcoin_server/libbitcoin_server.vcxproj.filters
build_msvc/libbitcoin_util/libbitcoin_util.vcxproj
build_msvc/libbitcoin_util/libbitcoin_util.vcxproj.filters
build_msvc/libbitcoin_wallet/libbitcoin_wallet.vcxproj
build_msvc/libbitcoin_wallet/libbitcoin_wallet.vcxproj.filters
build_msvc/libbitcoin_zmq/libbitcoin_zmq.vcxproj
build_msvc/libbitcoin_zmq/libbitcoin_zmq.vcxproj.filters
build_msvc/libbitcoinconsensus/libbitcoinconsensus.vcxproj
build_msvc/libleveldb/libleveldb.vcxproj
build_msvc/libleveldb/libleveldb.vcxproj.filters
build_msvc/libunivalue/libunivalue.vcxproj
build_msvc/libunivalue/libunivalue.vcxproj.filters
build_msvc/test_bitcoin-qt/test_bitcoin-qt.vcxproj
build_msvc/test_bitcoin-qt/test_bitcoin-qt.vcxproj.filters
build_msvc/test_bitcoin/test_bitcoin.vcxproj
build_msvc/test_bitcoin/test_bitcoin.vcxproj.filters
build_msvc/testconsensus/testconsensus.vcxproj

laanwj · 2017-10-20T13:30:37Z

Is there some tool to generate the vcxproj, vcxproj.filters and sln files programmatically from an easy-to-read text format that allows for easy tracking over time?

cmake can do that. Though I'm not sure about easy-to-read. Well easier to read than XML files, I guess. But I don't think adding an indirection step makes sense unless we'd use cmake as main build system, and that's certainly not planned and would probably piss of @theuni.
These files aren't really meant for reading, it's just the internal configuration of a GUI program.

If the VS build config gets added I will commit to maintaining it for a minimum of 3 years (end of 2020) excepting death, disability etc. As character assessment I've been an open source contributor since the early noughties: sourceforge, codeplex, bitbucket, github etc; no project highlights that will impress you guys but the relevant point is that I'm capable of hanging around.

Thanks. That's good enough for me :) You have the motiviation. You can never know for sure what happens in the future.

@jonasschnelli

I'd prefer an external gist/repository and maybe a link to that project (easier to remove if outdated).

Maybe - though it's easier for it to get lost in that case. There are AFAIK already tries at separate repositories with MSVC changes and build system, but they always get stuck at a certain version. Having it in the main repository is more of a incentive to keep it up to date. Probably.

laanwj · 2017-10-20T13:35:47Z

Maybe - though it's easier for it to get lost in that case. There are AFAIK already tries at separate repositories with MSVC changes and build system, but they always get stuck at a certain version. Having it in the main repository is more of a incentive to keep it up to date. Probably.

If we do go that route with a separate repository, we should create an 'official' repository under bitcoin-core at least instead of it only existing on some user's account.

An added advantage is that we can add @sipsorcery as committer. Delegating access is easier with separate repositories.

practicalswift · 2017-10-20T13:44:56Z

@laanwj I'm also thinking in terms of reproducibility. Adding 34 files to the main Bitcoin repo with a lot of redundancy (between files and within each file) that cannot be created from scratch using widely available free tools doesn't feel quite right (almost like having some magic binary blob in the repo!) :-) I suggest we go with an approach that makes changes to the build process (read diffs) easy to reason about.

This is an approach taken by another project - a simple shell script generating the files largely from what is already in the repo: https://github.com/robotdad/vclinux/blob/master/bash/genvcxproj.sh

On the other hand if this is not part of the main repo then perhaps we can have a lower bar with regards to readability/reproducibility/understandability/reviewability :-)

laanwj · 2017-10-20T13:48:05Z

We need an approach that makes changes to the build process (read diffs) easy to reason about.

Sure, that would be good, but the primary goal here is to make it easier for windows developers to build. And having to run a bash script isn't contributing to that.

Edit: THough we could have a generation script that is automatically run before releases, so the actual vcproj files would be part of the tarball but never the repository. Only developers using checkouts from git would then be required to run it themselves.

On the other hand if this is not part of the main repo then perhaps we can have a lower bar with regards to readability/reproducibility/understandability/reviewability :-)

Ok that would be another argument for having a separate repo.

practicalswift · 2017-10-20T13:50:33Z

build_msvc/bitcoind/bitcoind.vcxproj

+  </ItemGroup>
+  <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
+  <ImportGroup Label="ExtensionTargets">
+    <!--<Import Label="miniupnpcTarget" Project="f:\deps\miniupnpc\miniupnpc.targets" />-->


This can safely be removed? :-)

practicalswift · 2017-10-20T13:50:46Z

build_msvc/libbitcoin_server/libbitcoin_server.vcxproj

+  </ItemGroup>
+  <Import Project="$(VCTargetsPath)\Microsoft.Cpp.targets" />
+  <ImportGroup Label="ExtensionTargets">
+    <!--<Import Label="miniupnpcTarget" Project="F:\deps\miniupnpc\miniupnpc.targets" />-->


This can safely be removed? :-)

practicalswift · 2017-10-20T13:54:53Z

build_msvc/libbitcoinconsensus/libbitcoinconsensus.vcxproj

+      <PreprocessorDefinitions>WIN32;_DEBUG;_CONSOLE;%(PreprocessorDefinitions)</PreprocessorDefinitions>
+      <SDLCheck>false</SDLCheck>
+      <AdditionalIncludeDirectories>..\..\src;</AdditionalIncludeDirectories>
+      <LanguageStandard>stdcpp14</LanguageStandard>


Bitcoin is currently at C++11, so please change this instance of "stdcpp14" and the other four instances :-)

practicalswift · 2017-10-20T13:59:51Z

@laanwj I thought bash was widely available in Windows land these days thanks to the Windows Subsystem for Linux (WSL), but perhaps it is not yet as widely used as I thought :-)

practicalswift · 2017-10-20T14:02:41Z

@laanwj Good point about scripted generation that is automatically run before releases. Seems like a good solution!

sipsorcery · 2017-10-20T21:33:48Z

Attempting to generate the Visual Studio project files using a custom shell script will be a journey down the rabbit hole. Yes you might get a more succinct representation but maintaining the script would be a much larger burden.

The only viable approach I know of is to use cmake but even then you'll lose some devs due to the extra steps required. And while cmake is an excellent tool it does generate a lot of redundant configuration information in its VS config.

sipsorcery · 2018-08-10T07:20:53Z

@MarcoFalke sure, done.

maflcko · 2018-08-13T14:00:18Z

ACK ef7beae

ef7beae Visual Studio build configuration for Bitcoin Core (Aaron Clauson) Pull request description: This PR allows Bitcoin Core to be relatively easily built with Visual Studio 2017. It's anticipated that it could be useful for devs familiar with Visual Studio and Microsoft's tooling. In particular the ability to use the VS debugger is a big benefit. ~~Caveats:~~ - ~~There are some minor code changes required on Bitcoin Core in order for msvc to be able to successfully compile. I'll submit them in a separate PR, The code changes are available in bitcoin#11528 bitcoin#11558 and bitcoin#11562~~. - ~~The vcpkg for SECP256K1 has not yet been accepted by Microsoft. The files are available from this [PR](microsoft/vcpkg#2005) and should be copied into a vcpkg/ports/secp256k1 directory prior to vcpkg install steps.~~ **Update:** For anyone wishing to test out the Visual Studio build with the various open pull requests the steps are: - Clone and build [Vcpkg](https://github.com/Microsoft/vcpkg) (Microsoft's new open source C/C++ package manager) - git clone https://github.com/Microsoft/vcpkg - .\bootstrap-vcpkg.bat - Set up Visual Studio to automatically reference vcpkg installs: .\vcpkg integrate install - Install the required packages (replace x86 with x64 as required): - vcpkg install boost:x86-windows-static - vcpkg install libevent:x86-windows-static - vcpkg install openssl:x86-windows-static - vcpkg install zeromq:x86-windows-static - vcpkg install berkeleydb:x86-windows-static - vcpkg install secp256k1:x86-windows-static - vcpkg install leveldb:x86-windows-static - git clone https://github.com/bitcoin/bitcoin.git - git checkout -b testbuild - git pull origin pull/11526/head # Visual Studio build configuration for Bitcoin Core - ~~git pull origin pull/11558/head # Minimal code changes to allow msvc compilation~~ - ~~git pull origin pull/11562/head # bench: use std::chrono rather than gettimeofday~~ - ~~Copy and unzip attached bitcoin-config.h to src/config, edit as required [bitcoin-config.zip](https://github.com/bitcoin/bitcoin/files/1429484/bitcoin-config.zip)~~ - ~~git pull origin pull/13031/head # gmtime fix for msvc~~ - Build the Visual Studio solution which, if successful, will result in all but the Qt dependent libraries/programs being built. If the build fails please add a comment. Tree-SHA512: 5cd17273d33a09c35d8534c9f49123dec60ec05383669c67674b2cac88ada177bf94d7731c2a827759444f18d4b67085b91b02458124d0c32ab3a8f72ba5dac9

ysangkok · 2018-08-20T15:27:01Z

The commit description is wrong, the secp256k1 PR has been merged into vcpkg in Oct 2017: microsoft/vcpkg#2005

sipsorcery · 2018-08-20T17:01:17Z

@ysangkok not sure which commit message/comment you are referring to but yes I did a PR for libsecp256k1 and vcpkg at around the same time I did this PR. The upshot of it is that all the dependencies for building bitcoin core, sans the Qt projects, can be obtained with vcpkg.

ysangkok · 2018-08-20T17:07:37Z

I was referring to afa9600 . The issue seems to be that Git doesn't know about markdown so I couldn't see the strike-through...

e47dc4f Include bitcoin_config.h in release process (Hennadii Stepanov) 48ed65b Align MSVC build options with Linux build ones (Hennadii Stepanov) Pull request description: Ref: - #11526 - #15903 (comment) - #15903 (comment) by MarcoFalke ACKs for commit e47dc4: MarcoFalke: utACK e47dc4f Sjors: utACK e47dc4f fanquake: utACK e47dc4f practicalswift: utACK e47dc4f Tree-SHA512: 32ac3e9fd0b41a4916dd520bdf8bb6c71cea7218434b67a173b51b3cdb0da3f10a68b9e5205c27a52f456ac9ed14f8f8363a50d108a80a5dd55b085a6bd435b9

ghost · 2020-09-29T01:26:44Z

Build the Visual Studio solution which, if successful, will result in all but the Qt dependent libraries/programs being built.

Is it possible to build bitcoin core with Visual Studio 2019 including bitcoin-qt?

https://bitcoin.stackexchange.com/questions/99241/anyone-tried-building-bitcoin-core-with-visual-studio-2019

I even tried vcpkg install qt5 and vcpkg install qt5-base:x64-windows but didn't help

ef7beae Visual Studio build configuration for Bitcoin Core (Aaron Clauson) Pull request description: This PR allows Bitcoin Core to be relatively easily built with Visual Studio 2017. It's anticipated that it could be useful for devs familiar with Visual Studio and Microsoft's tooling. In particular the ability to use the VS debugger is a big benefit. ~~Caveats:~~ - ~~There are some minor code changes required on Bitcoin Core in order for msvc to be able to successfully compile. I'll submit them in a separate PR, The code changes are available in bitcoin#11528 bitcoin#11558 and bitcoin#11562~~. - ~~The vcpkg for SECP256K1 has not yet been accepted by Microsoft. The files are available from this [PR](microsoft/vcpkg#2005) and should be copied into a vcpkg/ports/secp256k1 directory prior to vcpkg install steps.~~ **Update:** For anyone wishing to test out the Visual Studio build with the various open pull requests the steps are: - Clone and build [Vcpkg](https://github.com/Microsoft/vcpkg) (Microsoft's new open source C/C++ package manager) - git clone https://github.com/Microsoft/vcpkg - .\bootstrap-vcpkg.bat - Set up Visual Studio to automatically reference vcpkg installs: .\vcpkg integrate install - Install the required packages (replace x86 with x64 as required): - vcpkg install boost:x86-windows-static - vcpkg install libevent:x86-windows-static - vcpkg install openssl:x86-windows-static - vcpkg install zeromq:x86-windows-static - vcpkg install berkeleydb:x86-windows-static - vcpkg install secp256k1:x86-windows-static - vcpkg install leveldb:x86-windows-static - git clone https://github.com/bitcoin/bitcoin.git - git checkout -b testbuild - git pull origin pull/11526/head # Visual Studio build configuration for Bitcoin Core - ~~git pull origin pull/11558/head # Minimal code changes to allow msvc compilation~~ - ~~git pull origin pull/11562/head # bench: use std::chrono rather than gettimeofday~~ - ~~Copy and unzip attached bitcoin-config.h to src/config, edit as required [bitcoin-config.zip](https://github.com/bitcoin/bitcoin/files/1429484/bitcoin-config.zip)~~ - ~~git pull origin pull/13031/head # gmtime fix for msvc~~ - Build the Visual Studio solution which, if successful, will result in all but the Qt dependent libraries/programs being built. If the build fails please add a comment. Tree-SHA512: 5cd17273d33a09c35d8534c9f49123dec60ec05383669c67674b2cac88ada177bf94d7731c2a827759444f18d4b67085b91b02458124d0c32ab3a8f72ba5dac9

…ones e47dc4f Include bitcoin_config.h in release process (Hennadii Stepanov) 48ed65b Align MSVC build options with Linux build ones (Hennadii Stepanov) Pull request description: Ref: - bitcoin#11526 - bitcoin#15903 (comment) - bitcoin#15903 (comment) by MarcoFalke ACKs for commit e47dc4: MarcoFalke: utACK e47dc4f Sjors: utACK e47dc4f fanquake: utACK e47dc4f practicalswift: utACK e47dc4f Tree-SHA512: 32ac3e9fd0b41a4916dd520bdf8bb6c71cea7218434b67a173b51b3cdb0da3f10a68b9e5205c27a52f456ac9ed14f8f8363a50d108a80a5dd55b085a6bd435b9 # Conflicts: # build_msvc/bitcoin_config.h # doc/release-process.md

fanquake added the Windows label Oct 19, 2017

practicalswift reviewed Oct 19, 2017

View reviewed changes

sipsorcery force-pushed the build_msvc branch from ca8ec95 to e745900 Compare October 19, 2017 13:21

sipsorcery force-pushed the build_msvc branch 2 times, most recently from b2a30bb to ccc5b6b Compare October 20, 2017 00:20

sipsorcery force-pushed the build_msvc branch from ccc5b6b to c304657 Compare October 20, 2017 06:26

sipsorcery force-pushed the build_msvc branch from c304657 to abd142f Compare October 20, 2017 07:44

practicalswift reviewed Oct 20, 2017

View reviewed changes

sipsorcery force-pushed the build_msvc branch from abd142f to 0a0684a Compare October 20, 2017 21:05

sipsorcery force-pushed the build_msvc branch from 0a0684a to dd5df9f Compare October 20, 2017 21:43

sipsorcery force-pushed the build_msvc branch from 9c8310a to ef7beae Compare August 10, 2018 07:19

maflcko merged commit ef7beae into bitcoin:master Aug 13, 2018

Bushstar mentioned this pull request Aug 13, 2018

commits from bitcoin/master FeatherCoin/Feathercoin#358

Merged

practicalswift mentioned this pull request Aug 24, 2018

ci: Add Appveyor CI #13964

Merged

hebasto mentioned this pull request Apr 27, 2019

docs: Align MSVC build options with Linux build ones #15908

Merged

jonatack mentioned this pull request May 23, 2019

build/doc: update bitcoin_config.h packages, release process #16080

Merged

sipsorcery deleted the build_msvc branch June 19, 2019 18:15

PastaPastaPasta mentioned this pull request Oct 8, 2021

Simpler Windows compilation on Windows platform / CMake support dashpay/dash#4496

Open

bitcoin locked as resolved and limited conversation to collaborators Feb 15, 2022

Visual Studio build configuration for Bitcoin Core #11526

Visual Studio build configuration for Bitcoin Core #11526

Uh oh!

Conversation

sipsorcery commented Oct 19, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

laanwj commented Oct 19, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sipa commented Oct 19, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

laanwj commented Oct 19, 2017

Uh oh!

practicalswift Oct 19, 2017

Choose a reason for hiding this comment

Uh oh!

practicalswift Oct 19, 2017

Choose a reason for hiding this comment

Uh oh!

jonasschnelli commented Oct 19, 2017

Uh oh!

meshcollider commented Oct 20, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sipsorcery commented Oct 20, 2017

Uh oh!

maflcko commented Oct 20, 2017

Uh oh!

sipsorcery commented Oct 20, 2017

Uh oh!

sipsorcery commented Oct 20, 2017

Uh oh!

practicalswift commented Oct 20, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

laanwj commented Oct 20, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

laanwj commented Oct 20, 2017

Uh oh!

practicalswift commented Oct 20, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

laanwj commented Oct 20, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

practicalswift Oct 20, 2017

Choose a reason for hiding this comment

Uh oh!

practicalswift Oct 20, 2017

Choose a reason for hiding this comment

Uh oh!

practicalswift Oct 20, 2017

Choose a reason for hiding this comment

Uh oh!

practicalswift commented Oct 20, 2017

Uh oh!

practicalswift commented Oct 20, 2017 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sipsorcery commented Oct 20, 2017

Uh oh!

sipsorcery commented Aug 10, 2018

Uh oh!

maflcko commented Aug 13, 2018

Uh oh!

ysangkok commented Aug 20, 2018

Uh oh!

sipsorcery commented Aug 20, 2018

Uh oh!

ysangkok commented Aug 20, 2018

Uh oh!

ghost commented Sep 29, 2020

Uh oh!

Uh oh!

sipsorcery commented Oct 19, 2017 •

edited

Loading

laanwj commented Oct 19, 2017 •

edited

Loading

sipa commented Oct 19, 2017 •

edited

Loading

meshcollider commented Oct 20, 2017 •

edited

Loading

practicalswift commented Oct 20, 2017 •

edited

Loading

laanwj commented Oct 20, 2017 •

edited

Loading

practicalswift commented Oct 20, 2017 •

edited

Loading

laanwj commented Oct 20, 2017 •

edited

Loading

practicalswift commented Oct 20, 2017 •

edited

Loading