...
You get points for not being on drive c
Ron
Haha, that my post, so thanks for the points.
It is impossible that gcc is not able to find the library, because I explicitly linked it in the specs file.
Nothing is impossible in computer science!
I'm not following OP's
Who's OP and where are his/her instructions?
instructions to the letter because they are confusing and lack detail (I do admire the initiative, but I'm not going to run any command or install every program just because someone on the internet says so).
Bravo. Me too.
There are also some errors in the post (you do not need to install perl for example, because it comes already with every MSYS or Git install).
Apparantly not all perl's are alike, at least as far as Qt or perhaps qmake are concerned!? Seems like way too much install baggage required to do a lowly compile for Windows
I also wonder why he is talking about a makefile.mingw and how to patch it, because I can't find it.
makefile.mingw is(was) the makefile used to create bitcoind.exe before the changeover to autogen, which happened between versions 0.8.6 & 0.9.0
All help is appreciated.
Jori.
Hello Jori,
A lot of "digital water" has flowed under the makefile "bridge" since nitrogenetics message # 1 in this forum! See
https://bt.irlbtc.com/view/149479.msg1587734#msg1587734 He has updated that message many times since the original March 05, 2013 message. I saved the original and still refer to it.
And since it has been updated, the comments back and forth about it, in this forum, may not seem to make sense, since they (the comments) refer to an original message # 1 that you cannot see.
But there are timeless comments (ahem!) on the art of compiling-linking software that should guide one to a working .exe file. See messages # 45 (page 3), 68 & 75 (page 4), 85 (page 5), 102 (page 6) and
bypassing all the bending over backwards that
gcc qmake and
makefile must do to run on or target Windows, message # 550 & 552 (page 28). These last two answer all the issues I posed in message # 85 on July 13, 2013. It's a
fait accompli since I have now built working versions of 3 other *coind.exe's and bitcoind.exe (YACoind.exe, Auroracoind.exe and Maxcoind.exe) all on MSVC++ Express all using the same four static multi-threaded libraries: Boost 1.53, OpenSSL 1.0.1g (!), Berkeley DB 4.8.30 and levelDB 1.13. It's pretty much build it (the libraries) and forget it. Also it's very easy to swap out a library. For example swapping out OpenSSL 1.0.1g for 1.0.1e or 1.0.1c was pretty much a no brainer. Same for flavors of Boost. Is 1.54 or 1.55 better than 1.53? Is level DB 1.16 better than 1.15, 1.13, 1.12 as far as bitcoin is concerned? On Windows?
Getting off the soapbox and high horse now... and going back to the
nose to the grindstone, salt mine, dungeon... Actually, to making the "how to build the libraries" video series for MSVC++. Imagine a video game walk through
GUI manipulation is much easier to understand by seeing rather than reading "how to".
Ron
