The correct compilation method of Osip on the NT Platform

Create a new project first. Many documents on the internet describe how to create a Win32 dynamic link library project,

The same is true here. Create a blank project and save it.
Similarly, osipparser2 under the src directory of osip2 version 3.0.1

Copy all the files in the directory to the root directory of the project we just created, and operate on vc6:
Project-add to project-Files
Add all source programs and header files to the project to save the project.
At this time, we can try to compile the project, and you will get a lot of error messages, the content is not

The osipparser2/XXXXX. h header file cannot be found.
　　
Processing: in Linux, we usually copy the header file and the Lib library.

To/usr/inclue;/usr/lib and other directories, when the C source program directly writes # include <XXX. h>

, You can directly find them. In VC, the same, the simplest way is to put the osip2 source code

The osipparser2 directory under the include directory in the package is copied directly to our windows

By default, the directory is included in tool-options-Dir of vc6.

In ectories, (if you know this step, you do not need to copy the file,

Add the directory where the Osip source code package is located). By default,

The directory is C:/program files/Microsoft Visual Studio/vc98/include.

At this time, we re-compile our project, smoothly compile and generate osipparser2.dll. At this moment,

Many documents on the Internet may directly say that this step will also generate the libs directory, which contains

The osipparser2.lib file is not generated here :)
　　
The simplest method is to directly create a project without further research.

Create a Win32 static Link Library Project and compile it directly to get the osipparser2.lib

.

-----------------------------------

-------------------
Above, we get the Osip parser development library, and then compile the complete Osip Association

The stack Development Library is also based on the above method, respectively, to create a dynamic link library project and a static Link Library project, only

Replace the file to be copied with The oSIP directory under SRC and The oSIP directory under include.

Osip2.dll and osip2.lib.

When compiling osip2.dll, you may get an error again. The content means that the link library cannot be found.

To copy the previously compiled osipparser2.lib To The oSIP project directory

Operations in Step 6:
Object/LiBr in project-setting-Link

Ary modules:
The contents such as kernel32.lib user32.lib... xxx. Lib are added at the end:

Osipparser2.lib
　
Save the project and compile it again to compile osip2.dll.

-----------------------------------

-------------------
Now we have a complete Osip development library.

Add osipparser2.lib and osip2.lib to the Project LINK parameters.

.