Building headless Bitcoin and Bitcoin-qt on Windows

[horstman]

So, i am still stuck on trying to compile the Litecoinwallet.

Could someone please tell me, if the provided steps on this guide are the same we should use for litecoin? Should we just download the required version of boost etc. for litecoin?

[old c coder]

So, i am still stuck on trying to compile the Litecoinwallet.

Could someone please tell me, if the provided steps on this guide are the same we should use for litecoin? Should we just download the required version of boost etc. for litecoin?

That would seem like a reasonable test plan, and see if the results are different. 

As a partial answer in another direction, see
https://asktom.cf/index.php?topic=349094.msg7186738#msg7186738
which is to say that you might consider building your Windows version using MSVS.

Ron

[old c coder]

So, i am still stuck on trying to compile the Litecoinwallet.

Could someone please tell me, if the provided steps on this guide are the same we should use for litecoin? Should we just download the required version of boost etc. for litecoin?

That would seem like a reasonable test plan, and see if the results are different. 

As a partial answer in another direction, see
https://asktom.cf/index.php?topic=349094.msg7186738#msg7186738
which is to say that you might consider building your Windows version using MSVS.

Ron

Code:

Bitcoin version v0.9.0.99-ga63f8b7-beta MSVC++ (Mon, 10 Mar 2014 13:37:03 -0400)

Using OpenSSL version OpenSSL 1.0.1g 7 Apr 2014
Default data directory E:\Documents and Settings\Ron\Application Data\Bitcoin
Using data directory J:\dataForBTCtestMSsaved\data saved of 2014-05-29
Using at most 125 connections (2048 file descriptors available)
Using wallet wallet.dat
init message: Verifying wallet...
dbenv.open LogDir=J:\dataForBTCtestMSsaved\data saved of 2014-05-29\database Err
orFile=J:\dataForBTCtestMSsaved\data saved of 2014-05-29\db.log
Bound to 0.0.0.0:8333
init message: Loading block index...
Opening LevelDB in J:\dataForBTCtestMSsaved\data saved of 2014-05-29\blocks\inde
x
Opened LevelDB successfully
Opening LevelDB in J:\dataForBTCtestMSsaved\data saved of 2014-05-29\chainstate
Opened LevelDB successfully
LoadBlockIndexDB(): last block file = 144
LoadBlockIndexDB(): last block file info: CBlockFileInfo(blocks=272, size=708180
64, heights=302929...303200, time=2014-05-28...2014-05-29)
LoadBlockIndexDB(): transaction index disabled
LoadBlockIndexDB(): hashBestChain=00000000000000001c659677a9bddc6c4f9b5efd3a9bfa
b1e9e68ac9df71f5fd  height=303200 date=2014-05-29 18:24:32
init message: Verifying blocks...
Verifying last 60 blocks at level 2
No coin database inconsistencies in last 0 blocks (0 transactions)
 block index           15187ms
init message: Loading wallet...
nFileVersion = 90099
Keys: 105 plaintext, 0 encrypted, 0 w/ metadata, 105 total
 wallet                 1141ms
init message: Loading addresses...
Loaded 13969 addresses from peers.dat  422ms
mapBlockIndex.size() = 303242
nBestHeight = 303200
setKeyPool.size() = 101
mapWallet.size() = 0
mapAddressBook.size() = 4
DNS seeding disabled
ext-ip thread start
net thread start
addcon thread start
opencon thread start
msghand thread start
dumpaddr thread start
init message: Done loading
receive version message: /Satoshi:0.8.1/: version 70001, blocks=304698, us=0.0.0
.0:0, them=47.20.195.150:8333, peer=192.168.0.10:8333
Added time data, samples 2, offset -26 (+0 minutes)
- Connect 61 transactions: 1281.25ms (21.004ms/tx, 11.338ms/txin)
ERROR: GetMyExternalIP() : connection to 91.198.22.70:80 failed
- Verify 113 txins: 27281.25ms (241.427ms/txin)
- Connect: 27437.50ms
UpdateTip: new best=0000000000000000331b583db82d0a219c69f9dac6498ccf1f89b350cf32
34e1  height=303201  log2_work=78.871948  tx=39733605  date=2014-05-29 18:24:57
progress=0.965662
ProcessBlock: ACCEPTED

[DogeHitman]

Did you set --with-qt-plugindir when configuring?

I finally managed to compile bitcoin-qt.exe but when I run it I get:

Code:

The procedure entry point 
_ZN10QClipboard7setTextERK7QStringNS_4ModeE could not be located in the dynamic link library

[MartinF]

Hello!
After trying a LOT to compile a QT wallet for windows (an altcoin) I could finally do it.
Now, I have only one problem. In the wallet, when I go to options -> debug/console, if I enter the command "help", it crashes and says runtime error.
And now, everytime I open the wallet, it crashes at start.
If I reboot my PC, the wallet opens again. If I run other commands like getinfo, getmininginfo, listtransactions, etc, they work fine.
The only problem is with "help". Does anyone know what's happening and how to fix it?

[DogeHitman]

Hello!
After trying a LOT to compile a QT wallet for windows (an altcoin) I could finally do it.
Now, I have only one problem. In the wallet, when I go to options -> debug/console, if I enter the command "help", it crashes and says runtime error.
And now, everytime I open the wallet, it crashes at start.
If I reboot my PC, the wallet opens again. If I run other commands like getinfo, getmininginfo, listtransactions, etc, they work fine.
The only problem is with "help". Does anyone know what's happening and how to fix it?

I had similar problems with a different version of Berkely DB installed I would get runtime errors. Are you using 4.8.30.NC?

[cyrilbf]

Hello I know this is not really the right topic but I try anyway.
I'm looking for how to change the alert key file (alert.cpp).
I initially thought it was a sha256 encryption but it only gives me 64 character so I must be mistaken.
if a competent person inform me I know him shook very grateful.

[Watermelondea]

I there like.. a pack of files i need to install? Cuz there is too many.

[MarKusRomanus]

I have sucessfully compiled Litecoin-Qt but had to do some extra steps .  8.7.1 can be compiled with qt 5.2.1 like in this thread's description, but no need for any src code changes, just the same bitcoin-qt.pro file mods.  You can use all the other same dependencies in this tutorial.  I had to modify the Makefile.Release before the compiling step.  removing  -llibeay32 and  -lssleay32 from the LIBS line.  Bitcoin was much easier to compile.. 8.6 , 9.1 and above all compiled with this tutorial... after a long learning curve, albeit!   One big thing I would add is that you must run the MinGW installer as Admin!  If you don't, it wont create the msys.bat file and give you use of the msys shell.

[MartinF]

Hello!
After trying a LOT to compile a QT wallet for windows (an altcoin) I could finally do it.
Now, I have only one problem. In the wallet, when I go to options -> debug/console, if I enter the command "help", it crashes and says runtime error.
And now, everytime I open the wallet, it crashes at start.
If I reboot my PC, the wallet opens again. If I run other commands like getinfo, getmininginfo, listtransactions, etc, they work fine.
The only problem is with "help". Does anyone know what's happening and how to fix it?

I had similar problems with a different version of Berkely DB installed I would get runtime errors. Are you using 4.8.30.NC?

Yeah, I'm using 4.8.30 NC. But I'm using another version of openssl. Everything else is the same as what OP posted.

[psionin]

Hi, I am getting a bunch of warnings when building boost and also when building litecoin-qt.

They look like this:

Code:

	Line 22: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 36: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]
	Line 50: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 61: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]
	Line 77: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 90: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]

Full: http://pastebin.com/NLdKjSZq

The boost version is 1_55_0 and is built using the configuration in the original post. Can these be disabled if not fixed?

[corsaro]

excellent guide. This is the best guide on the web, I think.

It is easily adaptable to every altcoin-qt so I finally was success to compile my preferite altcoin-qt.exe

Many thanks

[old c coder]

Hi, I am getting a bunch of warnings when building boost and also when building litecoin-qt.

They look like this:

Code:

	Line 22: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 36: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]
	Line 50: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 61: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]
	Line 77: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 90: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]

Full: http://pastebin.com/NLdKjSZq

The boost version is 1_55_0 and is built using the configuration in the original post. Can these be disabled

Yes

if not fixed?

Fixed, good question!  Perhaps if you look at the boost code referenced you might come up with a "fix".  I'm surprised you don't get a ton of other warnings from boost and the *coin code too!?

Ron

[psionin]

Hi, I am getting a bunch of warnings when building boost and also when building litecoin-qt.

They look like this:

Code:

	Line 22: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 36: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]
	Line 50: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 61: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]
	Line 77: ..\..\deps\boost/boost/bind/arg.hpp:37:22: warning: typedef 'T_must_be_placeholder' locally defined but not used [-Wunused-local-typedefs]
	Line 90: ..\..\deps\boost/boost/tuple/detail/tuple_basic.hpp:228:45: warning: typedef 'cons_element' locally defined but not used [-Wunused-local-typedefs]

Full: http://pastebin.com/NLdKjSZq

The boost version is 1_55_0 and is built using the configuration in the original post. Can these be disabled

Yes

if not fixed?

Fixed, good question!  Perhaps if you look at the boost code referenced you might come up with a "fix".  I'm surprised you don't get a ton of other warnings from boost and the *coin code too!?

Ron

So far I tried this commit from this ticket, and even included it at the local definition level, but I was still getting warnings in general.hpp.

Code:

#if BOOST_GCC >= 40700
#pragma GCC diagnostic push
#pragma GCC diagnostic ignored "-Wunused-local-typedefs"
#endif

#  define BOOST_CONCEPT_ASSERT_FN( ModelFnPtr )             \
    typedef ::boost::concepts::detail::instantiate<          \
    &::boost::concepts::requirement_<ModelFnPtr>::failed>    \
      BOOST_PP_CAT(boost_concept_check,__LINE__)

}}

#if BOOST_GCC >= 40700
#pragma GCC diagnostic pop
#endif

Even if it worked, it doesn't seem to be a good solution because there are so many definitions to go through. A similar method I haven't tried is to add __attribute__((unused)) to each typedef.

I added #pragma warning(disable:4101) to the top of init.cpp, but that didn't seem to work either.

Finally, I added -Wno-unused-local-typedefs to CFLAGS in makefile.mingw and QMAKE_CXXFLAGS_WARN_ON in bitcoin-qt.pro, and apparently that worked.



Not sure why I'm only getting these warnings (and two others - "FD_SETSIZE" redefined and include winsock2.h before windows.h). I used the boost config from the original post:

Code:

b2 --build-type=complete --with-chrono --with-filesystem --with-program_options --with-system --with-thread toolset=gcc variant=release link=static threading=multi runtime-link=static stage

By the way, Ron, great videos, I just built Litecoin-Qt last night in Visual Studio. Makes a lot of things easier. I'm no longer getting this horrible crash when closing the wallet, although I wish I could learn to debug it at the assembly level like this guy.

-Alex

[old c coder]

Hi Alex,

Even if it worked, it doesn't seem to be a good solution because there are so many definitions to go through. A similar method I haven't tried is to add __attribute__((unused)) to each typedef.

I added #pragma warning(disable:4101) to the top of init.cpp,

I thought that that was a MSVC++ statement only?  So are you talking about a MS compile here?  Of what, Litecoind or Bitcoind?   Litecoin-qt or Bitcoin-qt?

but that didn't seem to work either.

Finally, I added -Wno-unused-local-typedefs to CFLAGS in makefile.mingw and QMAKE_CXXFLAGS_WARN_ON in bitcoin-qt.pro, and apparently that worked.

Aren't those gcc flags?  So are you back in gcc here?  BTW, makefile.release & bitcoin-qt.pro for which/what coin and version?  I am compiling Bitcoind 0.8.6 (MS & gcc) & Bitcoin-qt 0.8.6 (gcc only) from one set of sources, and I have a Bitcoind 0.9.x (gcc & MS).  Are you by any chance referring to bitcoin-qt 0.9.x in your bitcoin-qt.pro?  We won't talk about Auroracoin maxcoin or YACoin here as that would muddy the waters even further

Not sure why I'm only getting these warnings (and two others - "FD_SETSIZE" redefined and include winsock2.h before windows.h). I used the boost config from the original post:

Code:

b2 --build-type=complete --with-chrono --with-filesystem --with-program_options --with-system --with-thread toolset=gcc variant=release link=static threading=multi runtime-link=static stage

By the way, Ron, great videos,

Thanks

I just built Litecoin-Qt last night in Visual Studio.

Are you mixing me up with Claire perhaps?  I didn't show anything in MSVS for any Qt version

Makes a lot of things easier. I'm no longer getting this horrible crash when closing the wallet, although I wish I could learn to debug it at the assembly level like this guy.

-Alex

I had luck (in MSVS that is) running in debug mode and single stepping up to an error.  Of course if the code is crashing before main() (static initialization, etc.) or after shutdown (destructor cascades, etc.) it becomes tougher

Tell us about what version of which coin you are building with MSVS and which version of MSVS too!  Mine are as in the videos, though I haven't shown the Bitcoind 086 & 09x yet, but soon   Having trouble integrating "protobuffer" into everything as I don't understand how the paymentrequest.proto "begets" "paymentrequest.pb.h if at all

Ron

[psionin]

I thought that that was a MSVC++ statement only?

Okay, that makes sense as to why it didn't work. In the topic about compiler warnings warnings, I'm compiling litecoin-qt (0.8.5.1) with Qt5.3.0 and MinGW/gcc.

Are you by any chance referring to bitcoin-qt 0.9.x in your bitcoin-qt.pro?

No, Litecoin, the .pro file is still named the same.

Are you mixing me up with Claire perhaps?

I used her Litecoin solution, but your videos helped me understand some things about MSVS project configuration.

Tell us about what version of which coin you are building with MSVS and which version of MSVS too!

It's VS2012 and I was building Claire's MSVS Litecoin, which is 0.8.6.2 according to the CodePlex page.

[Jori]

Ron, I'm so sorry. I will look into your YouTube videos soon. I'm finally done with exams do I have some time left now (preparing for studying mathematics!). Will post my reaction on them!

[old c coder]

Ron, I'm so sorry. I will look into your YouTube videos soon. I'm finally done with exams do I have some time left now (preparing for studying mathematics!). Will post my reaction on them!

Hi Jori,

Math is good.  There is a lot of innumeracy out there, and it's getting worse.  I'm told that 4 out of 3 people have difficulty with math

Ron

[zaqco]

64 bit binaries
64 bit binaries can be compiled by using the following toolchain:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/seh/x86_64-4.9.0-release-posix-seh-rt_v3-rev2.7z/download

All dependencies must be rebuilt with the above toolchain.
Openssl should be configured with:

Code:

Configure mingw64

Hello all.  I'm stuck here and worried that if I don't do it properly, that nothing will work properly so I thought I'd ask.
Where it says "All dependencies must be rebuilt with the above toolchain." do I have to go through the entire process again up until this point but using mingw64? 

Or do I only need to type "Configure mingw64" somewhere?  If so, where do I type it?

Sorry for the noob question.  Any info appreciated.

[nuggetbram]

64 bit binaries
64 bit binaries can be compiled by using the following toolchain:
http://sourceforge.net/projects/mingw-w64/files/Toolchains%20targetting%20Win64/Personal%20Builds/mingw-builds/4.9.0/threads-posix/seh/x86_64-4.9.0-release-posix-seh-rt_v3-rev2.7z/download

All dependencies must be rebuilt with the above toolchain.
Openssl should be configured with:

Code:

Configure mingw64

Hello all.  I'm stuck here and worried that if I don't do it properly, that nothing will work properly so I thought I'd ask.
Where it says "All dependencies must be rebuilt with the above toolchain." do I have to go through the entire process again up until this point but using mingw64? 

Or do I only need to type "Configure mingw64" somewhere?  If so, where do I type it?

Sorry for the noob question.  Any info appreciated.

Go back through the process replacing any instances of mingw in config commands (e.g Configure mingw64). You don't need to redone load the dependencies, only reconfigure them. You also need to specify mingw64 in your PATH variable before mingw32