GCC version Compilation Method of wxsqlite3

Asked by netizens, I found out the GCC Compilation Method of wxsqlite3.

Preparation tools:

1. codeblocks compiled version: (this version contains many tools and does not need to be configured any more. You can use it as needed :))

 

Download: http://code.google.com/p/portablecb/downloads/list? Can = 1 & Q = & colspec = filename + Summary + uploaded + releasedate + size + downloadcount

2. wxWidgets GCC library. (The content in the old Deng version is included. If you are not using the old Deng version, how can you download and compile it .)

3. source program of wxsqlite3.

 

After decompression, the directory structure is as follows:

After codeblocks is enabled, We need to configure a global variable.

For example: (the old Deng version has been configured)

Then Import build/wxsqlite3_vc9.sln in the wxsqlite3 directory

After the import, there will be two projects, the other is the demo program, you may learn how to use wxsqlite3.

Then, set the engineering properties of wxsqlite3, mainly the search path settings for some "header files" and "Libraries.

Wxsqliet3 has a lot of compilation configurations in the project. To illustrate the problem, select a unicode version dll as an example,

Other similarities ~

After setting the search path, you need to set the file name of the import/export database, because the wxWidgets library name generated by vs is different from that generated by GCC,

You need to set it here. :

Now: the Basic settings are complete. You can go back to the IDE to start compiling,

Select the configured compilation configuration in Build targets.

Right-click the wxsqlite3 project and choose build.

If there is no accident,

The following files should exist in the wxsqlite3 directory:

The DLL is the file we need. Other Engineering configuration methods are similar ~.

 

Note later:

Since the sqlite3 database was used, wrapper has used several times. Among them, wxsqlite3 has used the longest time and is also the most complete project.

It is undeniable that wxsqlite3 is elegant and easy to use, but it is not a problem recently.

To use the wxsqlite3 class, you must reference the wxwidget library in the project. My wxWidgets library is compiled by myself. In pursuit of performance,

Generally, the computer is streaking, but once the system is infected with the EXE virus, it is completely redone. When the previous project is maintained again, there is a big problem ~

You need to re-compile the wxWidgets library ~.

So now I can use a third-party library instead of a third-party library in the vs project as much as possible. If necessary, I must select open-source, troubleshoot problems, and try to use a very small library.

A large library is heavy.

I tried to transform the wxqlite3 class into a STD Version, but I found that it is too closely dependent on wxWidgets, and the labor of separation is too large, so I gave up ~.

Currently, vs database development works with the encrypted sqlite3 library in wxsqlite3 (only implement its encryption without its wrapper .) + Self-modified kompexsqlitewrapper.

If you select wxWidgets for UI library development, I will select wxsqlite3 .~~~

 

FishSeeWater@gmail.com