Quote from: Claire123 on March 02, 2014, 03:42:31 PM

Thank you for finding the upnp issue!

I have checked in a fix for the batch file. When I was first working on the miniupnp code to create a suitable project file, I forgot that I had copied the .in to a .h to get it all to build and work. My batch file doesn't put any meaningful information into those two strings but I don't think that will cause a problem. If it does, however, I can just create my own version of the .h file and copy it over to use for the miniupnp build.

As far as your Qt64 build issue, it sounds like an issue with dynamic vs static libs. The statement in the batch file that calls perl to change the build options from dynamic to static in the qmake.conf file must run correctly. If you are using a different version of VS, like 2010, then the batch file needs to modify a qmake.conf file in a different directory (as well as other changes) Also, if you start building and anything goes wrong, don't start over unless you have a clean copy of the qt distribution. It's pretty picky. I hope this helps.

Thanks for trying all this out--I really appreciate it!

By the way, I have never used mingw on this machine--a Win 8 64 bit. I did install mingw and built the bitcoin daemon only on another Windows system and that experience convinced me that something needed to change Grin

I am running on VS 2012 Ultimate, so that shouldn't be the problem. I finally gave up and downloaded the Qt from Digia that was already built.

I also found a problem with buildboost.bat though.

The bjam for x64 part works correctly, but the bjam for x86 is missing:
--toolset=msvc-11.0

With the result is it builds for the 12.0 toolset, and thus you can't link on x86 due to missing libs. Adding --toolset=msvc-11.0 solves it.