Installing OpenH323 under Windows - Revision history

Dana: /* For MSVC 6 follow these steps */

2013-01-21T15:03:07Z

‎For MSVC 6 follow these steps

Dana: /* For MSVC 6 follow these steps */

2013-01-21T15:02:35Z

‎For MSVC 6 follow these steps

Dana: /* For MSVC 6 follow these steps */

2013-01-21T15:02:05Z

‎For MSVC 6 follow these steps

Dana: /* Configure paths for compilation */

2013-01-09T13:22:05Z

‎Configure paths for compilation

Dana: /* Configure paths */

2013-01-09T13:19:41Z

‎Configure paths

Dana: /* Install PWLib library */

2013-01-09T13:17:23Z

‎Install PWLib library

Dana at 13:14, 9 January 2013

2013-01-09T13:14:58Z

Dana at 13:07, 9 January 2013

2013-01-09T13:07:52Z

Dana: /* Prerequisites */

2013-01-09T11:34:13Z

‎Prerequisites

Dana at 11:33, 9 January 2013

2013-01-09T11:33:10Z

@@ Line 68: / Line 68: @@
   assert.cxx
   C:/Program Files/Microsoft SDK/include/winsock2.h(1218) : error C2061: syntax error : identifier 'DWORD_PTR'
-  C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2146: syntax error : missing ';' before identifier 'Key'\\ C:/Program Files/Microsoft SDK/include/winsock2.h(1262) :
+  C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2146: syntax error : missing ';' before identifier
- error C2501: 'ULONG_PTR' : missing storage-class or type specifiers
+ 'Key'\\ C:/Program Files/Microsoft SDK/include/winsock2.h(1262): error C2501:
   ....

@@ Line 68: / Line 68: @@
   assert.cxx
   C:/Program Files/Microsoft SDK/include/winsock2.h(1218) : error C2061: syntax error : identifier 'DWORD_PTR'
-  C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2146: syntax error : missing ';' before identifier 'Key'\\ C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2501:
+  C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2146: syntax error : missing ';' before identifier 'Key'\\ C:/Program Files/Microsoft SDK/include/winsock2.h(1262) :
-   'ULONG_PTR' : missing storage-class or type specifiers
+ error C2501: 'ULONG_PTR' : missing storage-class or type specifiers
   ....

@@ Line 68: / Line 68: @@
   assert.cxx
   C:/Program Files/Microsoft SDK/include/winsock2.h(1218) : error C2061: syntax error : identifier 'DWORD_PTR'
-  C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2146: syntax error : missing ';' before identifier 'Key'\\ C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2501:   'ULONG_PTR' : missing storage-class or type specifiers
+  C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2146: syntax error : missing ';' before identifier 'Key'\\ C:/Program Files/Microsoft SDK/include/winsock2.h(1262) : error C2501:
   ....
@@ Line 86: / Line 87: @@
 :-Right-click on "Console Components files" and select "Build" from the menu. This will build ptclib.lib (or ptclibd.lib if you are building the "Win32 Debug" version).
 :-Right-click on "PTLib files and select "Build" from the menu to build ptlib.dll (or ptlibd.dll if you are building the "Win32 Debug" version).  Note that MERGESYM will be automatically built the first time you build either ptlib.dll or ptlibs.dll, which may require also building the "Win32 Release" version of Console and Console Components if that was not done previously. You may also receive some unimportant warnings which you can ignore.
 ====For VS.net follow these steps====

@@ Line 120: / Line 120: @@
 Note that the starting directory must be the same as the one where you installed PWlib.
 As for PWLib, there are three different projects that can be built as Debug or Release or No trace versions, for both MSVC 6 and VS.Net:
@@ Line 159: / Line 161: @@
 Release: VoiceAgeG729.dll <br>
-====For MSVC 6 follow these steps====
+====For MSVC 6 follow these steps:====
 # open the project file "\OPENH323\OPENH323.DSW"
@@ Line 167: / Line 169: @@
 # Right-click on "OpenH323dll files" and select "Build" from the menu to build openh323.lib and openh323.dll (or openh323d.lib and openh323d.dll if you are building the "Win32 Debug" version, or openh323n.lib and openh323n.dll if you are building the "Win32 No Trace" version).
-==== VS.Net users should follow these steps ====
+==== VS.Net users should follow these steps: ====
 # open the project file "\OPENH323\OPENH323.SLN"

@@ Line 111: / Line 111: @@
 ::- The H323 source code, which can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=80674
-=== Configure paths===
+=== Configure paths for compilation===
 Similar with what we have done for PWLib we have to add the next paths for Open H323 using the Tools-Options dialogue:
@@ Line 173: / Line 173: @@
 # select the build type as "Release", "Debug" or "No Trace" in the Build toolbar
 # Right-click on "OpenH323Lib" and select "Build" from the menu to openh323s.lib (or openh323sd.lib if you are building the "Win32 Debug" version, or openh323sn.lib if you are building the "Win32 No Trace" version).
 # Right-click on "OpenH323dll" and select "Build" from the menu to build openh323.lib and openh323.dll (or openh323d.lib and openh323d.dll if you are building the "Win32 Debug" version, or openh323n.lib and openh323n.dll if you are building the "Win32 No Trace" version).
-−
 ==Plugins and audio codecs==

@@ Line 7: / Line 7: @@
 For installing PWLib you have to build it. This chapter will guide you on this process step by step. <br>
-Pwlib can be installed using Microsoft Visual Studio 6.0 (MSVC) or Visual Studio .NET (VS.net)
+PWLib can be installed using Microsoft Visual Studio 6.0 (MSVC) or Visual Studio .NET (VS.net)
 ===Prerequisites===
@@ Line 13: / Line 13: @@
 The following are needed in order to build Pwlib successfully:
 :- MSVC 6 or at least VS.net 2003<br>
-:- The source code for Pwlib, which can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=80674 or from CVS<br>
+:- The source code for PWLib, which can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=80674 or from CVS<br>
 :- An archive extractor. Note that it needs to handle end of line characters properly. A proper suggestion might be WinZip
@@ Line 20: / Line 20: @@
 *Installing GNU Bison
 :The GNU Bison tool is required for compiling Pwlib. GNU flex is not a necessary requirement, but, if you want to recompile the "asnparser" utility for making changes in the ASN files that come with OpenH323, you will need to install it too.
 :If you are using MSVC 6, navigate to Tools-Options-Directories and add "C:\Tools" to the executable directory path.
 :If you use VS.Net, go to Tools-Options-VC++ Directories and add "C:\Tools" to the executable directory path.
@@ Line 28: / Line 27: @@
 :When the STL library for MSVC was introduced, some mistakes were made, sufficiently big enough to make Pwlib not to work correctly. These were eventually corrected in the newer, bug-free versions.
 :These files are included in the Pwlib source directory. Navigate to “\Pwlib\” and run MSVC_UPGRADE.BAT. This is a batch file that searches for the good files and replaces the old ones in the right places.
 === Configure paths for compilation===

@@ Line 2: / Line 2: @@
 This is a how to install OpenH323 on Windows platforms.
-===Install PWLib library===
+==Install PWLib library==
 We will start this section with the PWLib installation which is order to install OpenH323.
@@ Line 9: / Line 9: @@
 Pwlib can be installed using Microsoft Visual Studio 6.0 (MSVC) or Visual Studio .NET (VS.net)
-====Prerequisites====
+===Prerequisites===
 The following are needed in order to build Pwlib successfully:
@@ Line 33: / Line 33: @@
 :- the upgrading process begins. We recommend upgrading all the files with this patch (answer ''y'' to all questions<br>
 :- if your files are already upgraded, you will get a message like this: "C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\XTREE already upgraded. Press any key to continue . . ."-->
 The next step is to go to Tools-Options and add the following paths required for compilation:
@@ Line 39: / Line 41: @@
 :- pathto\PWLIB\LIB to the Executable directory list
 :- pathto\PWLIB\LIB to the Library directory list
 There are three different projects that can be built as Debug or Release versions, for both MSVC 6 and VS.Net:
@@ Line 50: / Line 54: @@
-======For MSVC 6 follow these steps======
+====For MSVC 6 follow these steps====
 :- open the project file “\PWLIB\PWLIB.DSW”
@@ Line 90: / Line 94: @@
 :-Right-click on "PTLib files and select "Build" from the menu to build ptlib.dll (or ptlibd.dll if you are building the "Win32 Debug" version).  Note that MERGESYM will be automatically built the first time you build either ptlib.dll or ptlibs.dll, which may require also building the "Win32 Release" version of Console and Console Components if that was not done previously. You may also receive some unimportant warnings which you can ignore.
-=====For VS.net follow these steps=====
+====For VS.net follow these steps====
 :- open the project file “PWLIB\PWLIB.SLN”. Ignore any warning about projects (e.g. "GUI.VCPROJ" not found”).
@@ Line 102: / Line 106: @@
   Right click on the "ASNParser" project and Select "Build" and the ASN Parser is installed.
-=== Install OpenH323 ===
+==Install OpenH323 ==
-Let’s continue now with the OpenH323 installation:
+Let’s continue now with the OpenH323 installation.
 Before proceeding, make sure that the Pwlib is compiled and installed. This was discussed above. Here you will be helped to install OpenH323 on Windows, using both MSVC and VS.Net.
@@ Line 112: / Line 116: @@
 :- The previous section's requirements including the compiled version of PWLib
 ::- The H323 source code, which can be downloaded from http://sourceforge.net/project/showfiles.php?group_id=80674
 Similar with what we have done for PWLib we have to add the next paths for Open H323 using the Tools-Options dialogue:
@@ Line 159: / Line 165: @@
 Release: VoiceAgeG729.dll <br>
-* Continuing, for MSVC 6 use these steps:
+====For MSVC 6 follow these steps====
 # open the project file "\OPENH323\OPENH323.DSW"
@@ Line 167: / Line 173: @@
 # Right-click on "OpenH323dll files" and select "Build" from the menu to build openh323.lib and openh323.dll (or openh323d.lib and openh323d.dll if you are building the "Win32 Debug" version, or openh323n.lib and openh323n.dll if you are building the "Win32 No Trace" version).
-* VS.Net users should follow these steps:
+==== VS.Net users should follow these steps ====
 # open the project file "\OPENH323\OPENH323.SLN"
@@ Line 176: / Line 182: @@
-===Plugins and audio codecs===
+==Plugins and audio codecs==
 Now let's talk a bit about the plugins and audio codecs. Codecs must be compiled from separate projects. After compilation, each project will make its own DLL. If you compile as a Release, the codec DLLs will be found in "\OPENH323\PLUGINS\RELEASE".<br>

@@ Line 29: / Line 29: @@
 :These files are included in the Pwlib source directory. Navigate to “\Pwlib\” and run MSVC_UPGRADE.BAT. This is a batch file that searches for the good files and replaces the old ones in the right places.
-If the batch fails, you will have to download manually from http://www.voxgratia.org/releases/msvc6chk.zip, unzip and run the upgrade with the command  "msvc6chk upgrade":
+<!--If the batch fails, you will have to download manually from http://www.voxgratia.org/releases/msvc6chk.zip, unzip and run the upgrade with the command  "msvc6chk upgrade":
 :- press ''y'' when asked "Upgrade file? (y/n)"<br>
 :- the upgrading process begins. We recommend upgrading all the files with this patch (answer ''y'' to all questions<br>
-:- if your files are already upgraded, you will get a message like this: "C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\XTREE already upgraded. Press any key to continue . . ."
+:- if your files are already upgraded, you will get a message like this: "C:\Program Files\Microsoft Visual Studio\VC98\INCLUDE\XTREE already upgraded. Press any key to continue . . ."-->
 The next step is to go to Tools-Options and add the following paths required for compilation:
@@ Line 49: / Line 49: @@
 : Debug: ptlibd.lib and ptlibd.dll Release: ptlib.lib and ptlib.dll
-*For MSVC 6 follow these steps
 :- open the project file “\PWLIB\PWLIB.DSW”
 :- make sure the "File view" tab is selected in the Workspace