Delphi：遵循h的视频会议系统代码.zip源码Delphi项目程序源码下载

Portable Windows Libary ======================= Contents -------- 1. Introduction 2. Apologies 3. CVS Access 4. Building PWLib 5. Using PWLib 6. IPv6 issues 7. Platform Specific Issues 8. Conclusion 9. Licensing ================================================================================ 1. Introduction --------------- PWLib is a moderately large class library that has its genesis many years ago as a method to product applications to run on both Microsoft Windows and Unix X-Windows systems. It also was to have a Macintosh port as well but this never eventuated. Since then the system has grown to having quite good application to areas other than mere Windows GUI portability. Classes for I/O portability, multi-threading portability, aid in producing unix daemons and NT services portably and all sorts of internet protocols were added over the years. All this over and above basic "container" classes such as arrays, linear lists, sorted lists (RB Tree) and dictionaries (hash tables) which were all created before STL became the answer to all our prayers. Unfortunately, due to intertia and the GNU C++ inadequate support of templates, this library will probably not be ported to STL in the near future. The library was used extensively for all our in-house products. Then we decided to support the open H323 project by throwing in some of the code written for one of our products. Thus, required PWLib so it got thrown into the open source world as well. ================================================================================ 2. Apologies (not) ------------------ As you start using the library, the inevitable question "why did they do it that way?" will come up. The more experienced out there will know that there are several reasons for the way things are: * Carefully considered design, * Workarounds for portability and compiler subtleties, * History, it may be too hard to change an early design decision, * Complete arbitrariness, the absence of any compelling reason. So, when you ask the next question "why didn't you do it this way?" The answer will be one of the above. The last one being a synonym for "we didn't think of that!" The bottom line is, use the library as is or change it as you require. You can even send in suggestions for improvements (or merely changes) and we may (or may not) include them in the base line code. Just do not send us any mail starting with the words "Why did you..." as the answer is quite likely to be "Because!" ================================================================================ 3. CVS Access ------------- There is a public CVS archive available at cvs.openh323.org. Note that there are still some parts of PWLib that are not available, so make sure you use the modules provided for check out and do not just try and check out "pwlib" on it's own. If you do all you will get is this file. The modules available are: ptlib_unix pwlib_xlib (does not work, anyone is welcome to fix!) ptlib_win32 pwlib_win32 ================================================================================ 4. Building PWLib ----------------- This library is multi-platform, however there are only two major build systems that are used. The Microsoft DevStudio environment for Windows and the GNU make system for all of the various unix systems. 4.1. For Windows ---------------- 1. Note you will need the bison and flex tools to compile some parts of the system. You can get a copy from http://www.openh323.org/bin/flexbison.zip, follow the instructions included in that package and put the executables somewhere in your path. 2. Start MSVC (v5, v6 or v7 (.NET)). If you have another compiler you are on your own! Add these folders to the Include Files path as follows: In VisualStudio v5/6 go into the Tools menu, Options item, Directories tab. In VisualStudio v7, go into the Tools menu, Options item. In the Options dialog, open the Projects folder, VC++ Directories item. In the 'Show Directories for:' list, select 'Include files'. C:\PWLib\Include\PwLib\MSWIN (if you have the full PWLIB version) C:\PWLib\Include\PtLib\MSOS C:\PWLib\Include Add the following to the Lib Files path and the Executable Files path: C:\PWLib\Lib The Lib folder is created as parts of PWLib are built. Also add this directory to your PATH environment variable (so PWRC, MergeSym and ASNParser tools can be found). 2a. If you have OpenSSL installed and compiled on your system then you can define the following environment variables to get SSL support: OPENSSLFLAG=1 OPENSSLDIR=c:\somewhere\openssl OPENSSLLIBS=ssleay32.lib libeay32.lib If you have NOT included these variables then you will get a warning during the build. YOu can safely ignore this warning. 2b. If you have EXPAT installed and compiled on your system then you can define the following environment variables to get XML support: EXPATFLAG=1 EXPATDIR=c:\somewhere\expat EXPATLIBS=expat.lib If you have NOT included these variables then you will get a warning during the build. YOu can safely ignore this warning. 3. In VisualStudio v5/6 open the pwlib.dsw file in the pwlib top directory. If you have the minimum library it will come up with several requests to find .dsp files, just cancel past these. In VisualStudio v7 open the pwlib.sln file in the pwlib top directory. 4. In VisualStudio v5/6 use the Batch Build command and build the "ASNParser Win32 Release", "pwtest Win32 Release" and "pwtest Win32 Debug" targets. Make sure all other targets are not checked. In VisualStudio v7 use the Batch Build command. It seems as though the batch build does not build dependent parts unless they're checked in the Build column. For a test build, be sure all Projects are checked except ASNParser-debug, MergeSym-debug, PacketVXD-release, PWRC-debug, and both XMLRPC. 5. That's it, now you're on your own! These are the project relationships: project dependencies output ------- ------------ ------ Console (none) ptlibs.lib GUI (none) pwlibs.lib MergeSym ptlibs.lib mergesym.exe PTLib ptlibs.lib, mergesym.exe ptlib.dll & lib PWLib pwlibs.lib, mergesysm.exe, ptlib.lib pwlib.dll & lib Console Components (none) ptclib.lib GUI Components (none) pwclib.lib ASN Parser ptlib.lib asnparser.exe PWRC ptlib.lib (flex.exe) pwrc.exe PWTest ptlib,pwlib,ptclib,pwclib.lib,pwrc.exe pwtest.exe MSDevWizard (none) PWLibWizard.awx XMLRPC ptlibs.lib, ptclib.lib xmlrpc.exe PacketVXD (none) epacket.vxd Debug versions append 'd' to filename, ie: ptlibsd.lib. MSDevWizard will not build in VisualStudio v7 and so is not included as a project. -------------------------------------------------------------------------------- 4.2. For unix. -------------- 1. If you have not put pwlib it into your home directory (~/pwlib) then you will have to defined the environment variable PWLIBDIR to point to the correct directory. Also make sure you have added the $PWLIBDIR/lib directory to your LD_LIBRARY_PATH environment va