Shulou(Shulou.com)05/31 Report--

This article mainly introduces the relevant knowledge of what is the method of compiling bitcoin by win10+vs2008. The content is detailed and easy to understand, the operation is simple and quick, and has certain reference value. I believe you will gain something after reading this win10+vs2008 method of compiling bitcoin. Let's take a look.

I. Source code

The bitcoin-0.1.0 version is used here.

Second, configure dependent libraries

A) wxWidgets (version 3.0.3)

Installation method: download the Windows ZIP version from http://www.wxwidgets.org/downloads/ and decompress it

Next, compile the wxwidgets file, here using the mingw32-make command, because I have installed codeblocks-13.12mingw-setup before, this step I can directly carry out, summary will not write, codeblocks installation is relatively simple. However, there are some problems with the configuration of environment variables. Forget the setting of environment variables, C:\ Program Files (x86)\ CodeBlocks\ MinGW\ bin

Enter the unzipped directory of wxwidgets on the command line and enter the following command:

Mingw32-make-f makefile.gcc MONOLITHIC=1 SHARED=1 UNICODE=1 BUILD=debug

This may take a long time.

B) openssl (version 1.0.2)

There will be a problem after 1.0.2 mentioned above, I did not try, it is not clear, the aim now is to compile and pass.

The installation method is the tricky method mentioned above.

C) Berkeley DB (version 4.8.30)

Here I download is the Windows installation, so there is no process of compiling the source code, it is still very simple.

D) Boost (version 1.63.0)

Use vs to import bitcoin source code from "source code import"

Here we use the src/ directory as the root directory.

Create a new directory, such as bitcoin, whatever. Then copy all the files in the src/ directory to this new directory. We now think of this new catalog as /. Subsequent descriptions are for / as the root directory.

Open vs

Click New

Create a project from existing code

Pop up the dialog box, select the default Visual C++, and click next

Fill in the location of the / directory just now, name the project name bitcoin-v0.1 or any other project name you like, and click next.

Use the visual studio-> project type to select "Windows Application Project" (that is, directly use the default). If the rest remains unchanged, click next.

Click finish

At this point, you have created a new project and imported the source code.

IV. Configuration

This is a crucial first step.

Now let's assume that the four dependent libraries just configured are all set to environment variables (if you don't set the environment variables, then you'll fill in the path when you configure the project's dependencies.)

Go back to the desktop-> right-click on this computer-> Properties-> Advanced system Settings-> Environment variables-> start creating environment variables in the section of system variables

Click New:

For example: wsWidgets = > then write WXWidgetsPath in the variable name, and then fill in the root directory where you just installed (unzipped) widgets

For the other three dependent libraries, a total of 4 environment variables are configured:

WXWidgetsPath

OpenSSLPath

BDBPath

BoostPath

Of course, the names of the above four environment variables are randomly chosen by me, and there is no agreement. You can choose the name you want according to your imagination. Take these four variables here and we will refer to these four variables in the configuration of the project, and then change your name to your own.

Close the project you just created and then restart it (this is to let vs load the environment variable you just took. If you don't have the environment variable configured, you don't need to restart vs)

Right-click the project you just created in the solution and select Properties.

A) set the unicode character set

Note that the configuration of this step is not required if your wxWidgets is an older version (it seems to be less than 2.8m?) Or if you choose to turn off the unicode switch when compiling wxWidgets libraries and compile libraries other than non-unicode wxWidgets libraries, you can skip this step and not set the unicode character set. Otherwise, the setup.h of wxWidgets will not find the path when the compilation is started.

If you are compiled by vs, be sure to set the unicode character set.

Find the project default value-character set in configuration Properties-General

Click the drop-down box and choose to use the Unicode character set

B) set VC++ dependencies

Find the include directory and library directory under the configuration properties-VC++ directory, click on the include directory, and fill in

$(WXWidgetsPath)\ include

$(WXWidgetsPath)\ include\ msvc

(note that the WXWidgetsPath here is the environment variable just configured. If it is not configured, just fill in the path of wxWidgets plus the path of include. The following is the same)

This introduces the header file path and lib path of the wxWidgets library.

Note: because the wxWidgets library is bound to windows applications and is not an ordinary C++ dependent library, it must be set in the part of VC++, otherwise, wxWidgets will not be able to compile.

C) set C++ dependency

Find "additional inclusion Catalog" in the configuration attribute-cUniverse +-General, click Edit, and fill in:

$(BoostPath)

$(OpenSSLPath)\ include

$(BDBPath)\ include

This introduces the header file path of boost,openssl, bdb.

Find "additional Library Catalog" in configuration Properties-Linker-General, click Edit, and fill in:

$(OpenSSLPath)\ lib

$(BDBPath)\ lib / / Note that this may change depending on your environment

(bold | eye-catching) the pit of oracle is reflected here. $(BDBPath)\ lib refers to the path to the libs of bdb, but! Because we are compiling a debug project, we can only introduce debug's dll (lib) later. (if normal, it would be possible to introduce release's lib, but for bdb, the debug project's dll using release will crash when running free ().

However, after the introduction of debug, the dll of debug in the source installation package seems to be problematic (bold), which will directly cause the program to crash! It is not clear whether I am alone or not. If this problem occurs, please recompile the debug version of bdb on your computer and replace $(BDBPath)\ lib with a new path, refer to the next article)

Find "additional dependency" in the configuration properties-linker-input, click Edit, and fill in:

Libeay32.lib

Libdb48d.lib / / Note that this is the dll library with'd', that is, debug.

Then open the explorer (just click my computer.) Find the directory of the project, create a libs/ directory under the root / directory of the project, and copy

Libeay32.dll under $(OpenSSLPath) directory

And

Libdb48d.dll under $(BDBPath)\ bin\ debug directory

Enter the libs directory.

Note that the dll of the problem just described is this libdb48d.dll. If something goes wrong, you probably need to replace it with your own compiled dll.

Then go back to the project configuration of VS

Find "command line" in configuration properties-build events-post-build events

Fill in:

Xcopy / y / d "$(ProjectDir) libs\ * .dll"$(OutDir)"

The libs for this command is the libs/ directory you just created under the root of the project. So this sentence means to copy all the dll in the libs/ directory to the output directory (here refers to the Debug directory)

5. Modify the source code

Error

1. Headers.h

Vc6++ conflicts with platforms above vc9

Because the source code should be compiled under the vc6++ platform, the predefinition of winnt must be removed first, otherwise there will be compatibility problems.

Find the headers.h file and find on line 10:

# ifdef _ WIN32_WINNT

# undef _ WIN32_WINNT

# endif

# define _ WIN32_WINNT 0x0400 / / Delete these four lines

Comment out or delete all four lines.

Windows.h and winsokc2.h order

Find the headers.h file on line 23 and find:

# include

# include

# include / / move windows.h to the bottom

Mobile windows.h to get

# include

# include

# include

Or introducing a macro can also solve the problem of introducing a windows.h header file:

# define _ WINSOCKAPI_ / / stops windows.h including winsock.h

# include

/ /...

# include "MyClass.h" / / Which includes

After that, find the net.cpp file, and line 5 exchange the header file to introduce

# include "headers.h"

# include / / swap these two lines as above

/ / = >

# include

# include "headers.h"

2. Clock11 conflicts with existing code

Std::array conflict between net.h/net.c boost::array and clock11

Find the net.h file and find it on line 419

Extern arrayvfThreadRunning; / / add Namespace

/ / modified to = >

Extern boost::arrayvfThreadRunning; / / add Namespace

Find the net.c file and make the same change on line 26

ArrayvfThreadRunning

/ / modified to = >

Boost::arrayvfThreadRunning

The bind function of winsock.h conflicts with std::bind

Find the net.c file, line 937

If (bind (hListenSocket, (structsockaddr*) & sockaddr, sizeof (sockaddr))

= = SOCKET_ERROR) / / bind function conflict

/ / change to = >

If (:: bind (hListenSocket, (structsockaddr*) & sockaddr

Sizeof (sockaddr)) = = SOCKET_ERROR) / / add:: global namespace

3. Serialize.h insert function const char* wants to cast to const_iterator

Find the serialize.h file and on line 808 find one based on the definition of the macro

# if! defined (_ MSC_VER) | | _ MSC_VER > = 1300

Void insert (iterator it, const char* first, const char* last)

{

Insert (it, (const_iterator) first, (const_iterator) last)

}

# endif

Modify to

# if! defined (_ MSC_VER) | | _ MSC_VER > = 1300

Void insert (iterator it, const char* first, const char* last)

{

Vector_type v (first, last)

Insert (it, v.begin (), v.end ())

}

# endif

4. Seems to be about the compatibility of MSVC8 allocator (uncertain)

Line 699 of the file serialize.h

Typedef vectorvector_type

/ / change it to = >, that is, remove the secure_allocator originally written by the author and use the one that comes with vector.

Typedef vectorvector_type

At the same time, because the typedef of vector_type is already equivalent to vector, the constructor of the CDataStream class should also be changed.

File serialize.h line 741, delete or comment out this constructor

/ / CDataStream (const vector&vchIn, intnTypeIn=0, int

VersionIn=VERSION): vch (vchIn.begin (), vchIn.end ())

/ / {

/ / Init (nTypeIn, nVersionIn)

/ /}

Line 40 of the file key.h

Typedef vector

CPrivKey

/ / = > the modification method is the same as above

Typedef vectorCPrivKey

5. Replacement of unicode characters

Ps: if you use a lower version of wxwidgets, you don't need to replace it if you don't open the unicode macro.

Line 74 of the util.cpp file

Long ret = RegQueryValueEx (HKEY_PERFORMANCE_DATA, "Global", NULL

NULL, pdata, & nSize)

/ / the string "Global" should be unicode = > supported by win32.

Long ret = RegQueryValueEx (HKEY_PERFORMANCE_DATA, L "Global", NULL

NULL, pdata, & nSize)

/ / or change to another version of win API

Long ret = RegQueryValueExA (HKEY_PERFORMANCE_DATA, "Global", NULL

ULL, pdata, & nSize)

Line 173

GetModuleFileName (NULL, pszModule, sizeof (pszModule))

/ / GetModuleFileName defined under the unicode macro is a wide-character version, which is directly replaced by the Acsii version = >

GetModuleFileNameA (NULL, pszModule, sizeof (pszModule))

Line 272

ReturnGetFileAttributes (psz)! =-1

/ / same as above = >

ReturnGetFileAttributesA (psz)! =-1

Line 274 of the util.h file

OutputDebugString (p1)

/ / same as above = >

OutputDebugStringA (p1)

6. Ui.cpp / ui.h error

Line 254 of ui.cpp, about the problem that wsString's iterator fill constructor cannot be automatically converted (perhaps not when the wxWidgets version is lower)

ReturnCDataStream (strData.begin (), strData.begin () + event.GetInt (), SER_NETWORK)

/ / replace with = >

Const char* s = strData.mb_str ()

ReturnCDataStream (s, s + event.GetInt (), SER_NETWORK)

Similar 2650, wsString to std::string conversion

Wtx.vOrderForm.push_back (make_pair (m _ staticTextLabel [I]-> GetLabel ()

StrValue))

/ / call wsString to ToStdString () = >

Wtx.vOrderForm.push_back (make_pair (m _ staticTextLabel [I]-

> GetLabel () .ToStdString (), strValue))

Line 1245 of ui.cpp, characters missing quotation marks

Ps: emphasize! The lack of quotation marks is due to the fact that this is a very strange character in the original source code that was escaped when it was opened after importing vs. So here? It actually represents the original character. But this function is of no use, so just correct it here, and you don't have to restore the original meaning.

If (str.Find ('?)! = wxNOT_FOUND)

Str.Remove (str.Find (1))

/ / add missing quotation marks

If (str.Find ('?')! = wxNOT_FOUND)

Str.Remove (str.Find (?), 1)

2890 lines, wide characters

_ CrtSetReportFile (_ CRT_WARN, CreateFile ("NUL", GENERIC_WRITE, 0, NULL)

OPEN_EXISTING, 0,0))

/ / = >

_ CrtSetReportFile (_ CRT_WARN, CreateFile (L "NUL", GENERIC_WRITE, 0, NULL)

OPEN_EXISTING, 0,0))

2913 lines, ditto

HWND hwndPrev = FindWindow ("wxWindowClassNR", "Bitcoin")

/ / = >

HWND hwndPrev = FindWindow (L "wxWindowClassNR", L "Bitcoin")

3148 lines, the AddPendingEvent () function is obsolete for versions of wxWidgets above 3.0, and you need to rely on eventhandler to call.

/ / pframeMain- > AddPendingEvent (event)

PframeMain- > GetEventHandler ()-> AddPendingEvent (event)

7. Remove compatibility problems caused by cross-platform

Line 161 of the file util.h

Inline string i64tostr (int64 n)

{

Returnstrprintf ("%" PRId64, n)

/ / the PRId64 is brought across platforms and modified to the following code

/ / = > because we don't care about cross-platform issues and only limit the environment to win64, we don't have to worry about int64.

Returnstrprintf ("l", n)

}

8. Modifications after berkeleydb version 6.2 + are compatible (do not consider using version 4.7 or 4.8)

Line 18 of the file db.cpp

DbEnvdbenv (0)

/ / = >

DbEnvdbenv ((u_int32_t) 0)

Warning

Most of the warnings in the source code are due to the implicit conversion of symbols, which can be modified according to your own needs.

6. Solve the problem of wx dependent library

Http://www.cnblogs.com/waynecheng/archive/2012/04/18/2455765.html

After modifying the source code according to the above method, the "wx/msw/wx.rc" will not be found. You need to import the resource file, set the resource directory, project-> Properties-> Resources-> General-> additional include directory: e:\ wxWidgets-3.0.3\ include

Then there will be a lot of error LNK2019: unparsed external symbols, this kind of error, which requires recompiling wx, as follows:

Go to the E:\ wxWidgets-3.0.3\ build\ msw directory, Visual Studio 2008 open wx_vc9.sln, build the solution, and then you will see the vc_lib folder generated under\ lib, including the corresponding .lib and other files and the mswud folder. At this point, the wxWidgets is compiled.

Project setting

Right-click Project-> Properties-> Cramp Clippers-> General

[additional inclusion directory] = "$(wxWin)\ lib\ vc_lib\ mswud"

Project Properties-> Connector-> General

[additional library directory] = "$(wxWin)\ lib\ vc_lib\"

Project Properties-> Connector-> input

[additional dependencies] =

Wxmsw29ud_core.lib

Wxbase29ud.lib

Wxtiffd.lib

Wxjpegd.lib

Wxpngd.lib

Wxzlibd.lib

Wxregexud.lib

Wxexpatd.lib

Winmm.lib

Comctl32.lib

Rpcrt4.lib

Wsock32.lib

Odbc32.lib

Just compile and run again.

VII. Operation

The above part is only to solve the problems in the compilation time, the main thing is to make bitcoin run (miserably).

Next, I'll describe in detail how to modify the code to make bitcoin work.

I'm so tired.

Here, I'm just talking about the problems I've encountered.

I won't say the reason, and I don't understand it. I'll solve it directly.

Since neither release nor debug in the installation package can run, I have to compile the lib and dll of Berkeley DB by myself.

Suppose the root directory of the current berkeleydb is\

Then you can find Berkeley_DB.sln in the\\ db-4.8.30\ build_windows directory.

After opening it for upward compatibility, build the project, and then set an example project to run as the master project. If it can run successfully, it is built successfully and can run normally.

At this point, you can find libdb48d.lib and libdb48d.dll files in the\\ db-4.8.30\ build_windows\ Win32\ Debug\ directory. These two files are dynamic link libraries compiled on their own platform.

After that, modify the dependent library of the bitcoin source code about Berkeley DB to the new path, and then it can run normally.

The modified path here is $(BDBPath)\ db-4.8.30\ build_windows\ Win32\ Debug\

Then copy the libdb48d.dll to the libs directory of the bitcoin project.

This is the end of the article on "how win10+vs2008 compiles Bitcoin". Thank you for reading! I believe everyone has a certain understanding of "what is the method of compiling bitcoin by win10+vs2008". If you want to learn more, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.