Topic: Building headless Bitcoin and Bitcoin-qt on Windows - page 54. (Read 419389 times)

Openssl configured as follows from MSYS (I use msys-perl from MSYS as strawberry perl behaved strangely while configuring openssl)

Added LIB and INCLUDE environment variables (I added them via control panel, but doing it from cmd should be exactly the same)

Configured qt as follows

Then removed LIB and INCLUDE environment variables and built the project.



I also had a look at compiling a statically linked version of the executable, it works but there is no spinner shown while downloading blocks  
If you want to give it a try you need to compile qt statically


Set LIB and INCLUDE environment variables

Then edit bitcoin-qt.pro by adding

And edit QMAKE_LFLAGS by adding the -static flag

Then build from cmd or qt creator

Can you post the command-line you used for building OpenSSL? I really would like to find out, why that -openssl-linked is giving me errors :-/.
I've been building OpenSSL 1.0.1e with Configure --prefix=$PWD/dist no-idea no-mdc2 no-rc5 shared mingw like mentioned here:
https://qt-project.org/wiki/Compiling-OpenSSL-with-MinGW

Are we still talking about my command-line from above or yours for building Qt?

Dia

Ruby seems to be required to build QtWebKit, so it's not needed.

I compiled shared openssl libraries and then configured qt with -openssl-linked. It built with no problems, the generated bitcoin-qt asks for ssleay32.dll and libeay32.dll if it doesn't find them.

However, it's not clear to me what -openssl-linked really does. Here is an interesting comment I found on qt project forums:

I don't seem to need Ruby to build Qt, don't even know what that is for ^^. I'm using ActivePerl and Python 2.7.5.
That compilation error can be fixed by my pull here: https://github.com/bitcoin/bitcoin/pull/2826

Do you have an idea, why I can't seem to use -openssl-linked to build Qt 5.1 I have no clue and tried "everything".

Dia

Dia

I confirm bitcoin-qt (latest from master branch) compiles successfully with gcc-x32-4.8.1-release-posix-dwarf-rev2.
You can build qt 5.1 libraries without icu and openssl.

After installing and adding to path Strawberry Perl 5.18, Python 2.7 and Ruby 2.0 I configured qt as follows


Had to disable ipv6, or it would complain like this:

As Yogi Berra once said: "It's deja vu all over again!" See message #1! The first link in step 1.1 is that link! I referenced it in message #102,
https://bitcointalksearch.org/topic/m.2729273 from 3 days ago.

I'm happy with my windows "environment". I merrily make changes and just do the one compile (make) line for bitcoind or bitcoin-qt.

BTW, I offered Gavin
https://github.com/bitcoin/bitcoin/issues/2290
for a more "deterministic" build. Works for me! I can now change variable/function/method/member names and produce the same .exe binaries! Unfortunately If I move a global definition from one file to another, the .exe binary changes, and if I remove an unused/uncalled/unreferenced function (yes there is at least one!), the binary .exe changes, so no "joy" there.

Ron

You need to install mingw-get-inst-20120426 with pre packaged repositories
http://sourceforge.net/projects/mingw/files/Installer/mingw-get-inst/mingw-get-inst-20120426/

Understood.  Though, I'm still unclear on how to make Mingw use the right gcc version.  Their website doesn't seem to have any specific directions for doing so, and all the pre-packaged mingw installers I can find come with gcc 4.7, which means I'd still have to manually patch it with gcc 4.6.2, correct?

It simply prepares system prerequisites and builds qt, it is also mentioned on the official wiki http://qt-project.org/wiki/MinGW-64-bit


I'll give it a try


http://sourceforge.net/projects/msys2/
It's from the same authors of mingw-builds 

I don't really like such all-in-one build-scripts, as I want to know what is going on. Can you try to build Qt with compiler x32-4.8.1-release-posix-dwarf-rev2 and my short batch file from above? I'm sure you need to compile OpenSSL before or need to change the -openssl switch into -no-openssl.

Didn't know there was an MSYS2, where did you get that?

Dia

Better starting from scratch on a clean vm (see first post)

Ok, it seems I got it working, here is what I did:

-Installed MSYS2, cloned and configured qt-builds. See: https://github.com/Alexpux/Qt-builds/
-Modified buildall to get the latest x32-4.8.1-release-posix-dwarf-rev2.7z and x64-4.8.1-release-posix-seh-rev2.7z
-Built Qt 5.1.0 (took ~3.5 hours, qt-creator failed) -Built openssl (os must be manually specified) -Built DBD (os must be manually specified) -Built miniupnpc (double clic mingw32make.bat)
-Built leveldb (the usual way)
-Added dependency library locations to bitcoin-qt.pro, disabled leveldb generation then

Disabling ipv6 was necessary, otherwise compilation would fail (You can see a more detailed error when building from qt-creator )

Well, that would probably help.

I found a gcc 4.6.2 package....but I'm not quite sure how to go about rolling back Mingw's 4.7 package.  Looking at the info on mingw's site didn't help much, I still have no idea how to figure out what should be going where, since it appears there are files with 4.7.2 in the name sprinkled all over mingw's various directories.

Any input for someone more experienced with this program would be very helpful, I'm hesitant to mess with anything at this point for fear I'll accidentally nuke my whole mingw install.

Many thanks to nitrogenetics and old c coder, by the way, for being patient with us newbs.  Your advice is invaluable.

Nice that you are playing around with Qt 5.1 also , here is my configure.bat call, perhaps we can exchange some information. I seem to be unable to use the -openssl-linked parameter, I don't get it to compile.

Here is my batch-file to compile Qt 5.1:

Make sure you are compiling with gcc 4.6.2 if using precompiled qt 4.8.5 libraries.

Had a quick look at building with Qt 5.1 as suggested by Diapolo, but it seems BDB doesn't like gcc-4.8.0-dwarf-rev1 (also tried a precompiled gcc-4.8.1-dwarf-rev1 version from http://sourceforge.net/projects/mingwbuilds/files/external-binary-packages/Qt-Builds/ with the same results) gcc-4.8.1-dwarf-rev2 works, now I'm trying to compile Qt 5.1 with gcc-4.8.1-dwarf-rev2 toolchain.

Hey guys, I'm back.

Still having an issue trying to get bitcoin to run.  In post #70 I detailed the BEX error I was getting.

So, I found an 8.3 version of bitcoin (checked clientversion.h to make sure it really WAS 8.3).  So I compiled it, and I'm still getting the same BEX error.  I even disabled DEP completely using the command line on my system. (Windows 7 64 bit, if that makes any difference).  It stops giving me the BEX error, but now I just get an APPCRASH error:

Problem Event Name:   APPCRASH
  Application Name:   bitcoin-qt.exe
  Application Version:   0.8.3.0
  Application Timestamp:   51e57100
  Fault Module Name:   StackHash_0a9e
  Fault Module Version:   0.0.0.0
  Fault Module Timestamp:   00000000
  Exception Code:   c0000005
  Exception Offset:   00cd38e8
  OS Version:   6.1.7601.2.1.0.768.3
  Locale ID:   1033
  Additional Information 1:   0a9e
  Additional Information 2:   0a9e372d3b4ad19135b953a78882e789
  Additional Information 3:   0a9e
  Additional Information 4:   0a9e372d3b4ad19135b953a78882e789

For the record, I'm using MinGW (GNU bash ver. 3.1.17(1)), Active Perl 5.16.3 Build 1603 (64-bit), BOOST 1.54.0, DB 4.8.30 NC, Openssl-1.0.1e, and QT 4.8.5.

Am I using the wrong version of something?  Could my 64 bit system simply not like a custom-compiled bitcoin exe?  I know bitcoin will work on the system because I've installed it before. (Already checked to make sure the uninstall was clean)

Would a different version of bitcoin help at all?  Should I go all the way back to an 8.0 version?  Or would taking the .exe I made and running it, say, in a 32 bit XP virtual machine help at all?

And why does it seem to be crashing constantly on the StackHash 0a9e module?  What exactly is it here that windows just won't play nice with?

Any help would be appreciated....it's maddening to be so close to having it working.

That's the thing, they are in the path and I have checked all the known files to make sure everything is in place and pointed correctly.

It should be found and I cannot find out why, I does not make sense.

It means the header that is included is not found, straight forward error .
Check where your OpenSSL headers are, if you have them in your path or in the MinGW include dir.

Dia

I am getting this error.

Anyone know what it means please?

C:\Defaultcoin\Defaultcoin-Master>mingw32-make -f Makefile.Release
g++ -c -pipe -O2 -frtti -fexceptions -mthreads -fdiagnostics-show-option -Wall -Wextra -Wformat -Wformat-security -Wno-unused-parameter -DUNICODE -DQT_LARGEFILE_SUPPORT -DQT_GUI -DBOOST_THREAD_USE_LIB -DBOOST_SPIRIT_THREADSAFE -DBOOST_THREAD_PROVIDES_GENERIC_SHARED_MUTEX_ON_WIN -D__NO_SYSTEM_INCLUDES -DWIN32 -D_MT -DQT_DLL -DQT_NO_DEBUG -DQT_GUI_LIB -DQT_CORE_LIB -DQT_HAVE_MMX -DQT_HAVE_3DNOW -DQT
_HAVE_SSE -DQT_HAVE_MMXEXT -DQT_HAVE_SSE2 -DQT_THREAD_SUPPORT -DQT_NEEDS_QMAIN -I"..\..\Qt\4.8.4\include\QtCore" -I"..\..\Qt\4.8.4\include\QtGui" -I"..\..\Qt\4.8.4\include" -I"src" -I"src\json" -I"src\qt" -I"..\..\Qt\4.8.4\include\ActiveQt" -I"build" -I"build" -I"..\..\Qt\4.8.4\mkspecs\win32-g++" -o build\bitcoin.o src\qt\bitcoin.cpp
In file included from src/main.h:9:0,
                 from src/wallet.h:9,
                 from src/init.h:9,
                 from src\qt\bitcoin.cpp:11:
src/bignum.h:11:24: fatal error: openssl/bn.h: No such file or directory
compilation terminated.
mingw32-make: *** [build/bitcoin.o] Error 1

As to being able to make a change and be able to compile and run, perhaps this may help, if you are speaking of bitcoin-qt.

There may be a step between nitrogenetics' 4.1 and 4.2
See the file qtvars.bat in drive:\Qt\4.8.4\bin or where ever you installed Qt. You may need to "tailor" it to your specifications so that Windows knows where to "get stuff"? Just a thought.

I have no idea what it means to "clone Bitcoin". Nor what "scrypt" is. Nor what a GPU driver is, nor its relationship to SHA-256 on Windows or Linux?

Windows is no different from Linux or any other OS, if you have been in from the beginning and know all the historical, undocumented "gotchas", quirks, oddities, etc. Forward and back slashes, shell scripts in Linux vs .bat or .wsh scripts in Windows, etc. etc.

Ron