Codejock. Xtreme. toolkit. Pro. v13.2.1 personal corrections for installation and compilation

I downloaded this article from the library and installed and compiled it. The environment is vc6.0 and 2005 (vc8.0) + codejock. xtreme. toolkit. pro. v13.2.1 (csdn download ),

It mainly corrected the compilation selection and the correspondence between the generated libraries. In addition, for vc6.0, which is still widely used,

Project -- option --- configured in the directory, which is automatically configured after installation and compilation, without manual Configuration

In addition, three times of compilation, three options are compiled once, and 12 library files should be generated in the directory. However, if the first option is to compile only two libraries, an error is returned, ended. I do not know why, but it does not affect the execution of the program. Finally, I installed the program and created a new Xtreme under vc6.0. toolkit. warziad project, based on the single dialog box, without any code, compiled, OK, no prompt for missing Library

This library is very useful in VC. With the help of a good friend, you can quickly install it. Here are the detailed steps:

1. Download codejock. Xtreme. toolkit. Pro. v13.2.1 first (this version does not support 2010)

2. Perform the next step during installation.

3. A new configuration window will be displayed after the installation. Here you can check whether you need to select the Unicode version.

Or DLL or static Lib. We recommend that you do not need to include DLL when using Lib for release.

4. After the selection is complete, a cmd window will pop up to start self-compilation. The process is from 5 minutes to 10 minutes.

5. After compilation, You can compile the example. Make the settings before compilation. In project> setting> General> Microsoft Foundation Classes, select

Use MFC in a static library can be compiled.

 

Static link considerations
1) Static link to xtp when the program is dynamically linked to the MFC Library

2) When the program is dynamically static to the MFC library, it is statically linked to the xtp

In either case, you can configure _ xtp_staticlink to enable static connections. Remember to include the following statement in the RC2 file of your project during static connections. Otherwise, resources in xtp will be called.

An exception occurred.

# Include <xttoolkitpro. rc>

During toolkit installation, compilation of the corresponding Lib is very slow. At that time, I only generated a static library. They are:

Toolkitpro1321vc80s. Lib

Toolkitpro1321vc80sd. Lib

Toolkitpro1321vc80su. Lib

Toolkitpro1321vc80sud. Lib

S indicates static, d Indicates debug, and u indicates Unicode,

// Three options are available during compilation.

A) as DLL

B) as static library, for using MFC as DLL

C) as static library, for using MFs as static library.

// I have selected B. Therefore, the above libs: S is generated. lib, SD. lib, Su. lib, Sud. lib. // here is the error. It should be generated by C.

// If C is selected, DS is generated. lib, DSD. lib, DSU. lib, dsud. lib // The preceding D indicates that using MFC as DLL // should be generated by B.

// If A is selected, "". dll, D. dll, U. dll, Ud. dll.

 

Assume that the Xtreme toolkit is installed in: C: \ Program Files.

For example, the following directory exists: C: \ Program Files \ codejock SOFTWARE \ MFC \ Xtreme toolkitpro v13.2.1 \ Source

Modify the following settings in the project properties:

A) C/C ++ | General | add the "C: \ Program Files \ codejock SOFTWARE \ MFC \ Xtreme toolkitpro v13.2.1 \ source" to the included directory"

B) linker | General | additional library Directory: Add "C: Program Files \ codejock SOFTWARE \ MFC \ Xtreme toolkitpro v13.2.1 \ Lib \ vc80"

C) linker | input | ignore a specific library and add "libcd. lib ". If you follow the document, you also need to ignore more. I entered this first.

D) Resource | General | Add the inclusion directory and add "C: \ Program Files \ codejock SOFTWARE \ MFC \ Xtreme toolkitpro v13.2.1 \ source"

Then, modify the Code as follows:

A) Add # include "xttoolkitpro. H" at the end of stdafx. h"

B) add # include "xttoolkitpro. RC" at the end of XX. RC2"

C) then add the inheritance relationship to the Declaration in mainfrm. h:

Class cmainframe: Public cxtpmdiframewnd

Then the compilation is successful.

 

Note: Do not add any Xtreme toolkit to the project. Previously, I added xtpresource. H, xttoolkitpro. H, and xttoolkitpro. RC to the project. However

Cvt1100: duplicate resource, type: bitmap,... error.

 

Considerations for dynamic compilation
In fact, it is similar to static compilation. For static compilation, refer to my previous "Xtreme toolkit static compilation considerations", but copy the. dll of Xtreme toolkit to system32.

. Or put it in the output directory of exe.