文件列表:

pjproject-2.0-alpha2 (0, 2011-10-10)
pjproject-2.0-alpha2\aconfigure (451451, 2011-08-24)
pjproject-2.0-alpha2\aconfigure.ac (39954, 2011-08-24)
pjproject-2.0-alpha2\build (0, 2011-10-10)
pjproject-2.0-alpha2\build\cc-auto.mak.in (414, 2010-08-25)
pjproject-2.0-alpha2\build\cc-gcc.mak (524, 2006-05-11)
pjproject-2.0-alpha2\build\cc-vc.mak (426, 2005-11-21)
pjproject-2.0-alpha2\build\common.mak (1506, 2010-05-17)
pjproject-2.0-alpha2\build\host-mingw.mak (317, 2005-11-21)
pjproject-2.0-alpha2\build\host-unix.mak (302, 2010-08-05)
pjproject-2.0-alpha2\build\host-win32.mak (353, 2005-11-21)
pjproject-2.0-alpha2\build\m-alpha.mak (106, 2005-11-21)
pjproject-2.0-alpha2\build\m-arm.mak (106, 2006-07-14)
pjproject-2.0-alpha2\build\m-auto.mak (36, 2006-08-21)
pjproject-2.0-alpha2\build\m-i386.mak (105, 2005-11-21)
pjproject-2.0-alpha2\build\m-m68k.mak (105, 2005-11-21)
pjproject-2.0-alpha2\build\m-mpc860.mak (247, 2006-05-11)
pjproject-2.0-alpha2\build\m-powerpc.mak (108, 2006-03-20)
pjproject-2.0-alpha2\build\m-sparc.mak (106, 2005-11-21)
pjproject-2.0-alpha2\build\m-x86_64.mak (107, 2006-07-23)
pjproject-2.0-alpha2\build\os-auto.mak.in (198, 2010-08-25)
pjproject-2.0-alpha2\build\os-darwinos.mak (179, 2006-08-21)
pjproject-2.0-alpha2\build\os-linux-kernel.mak (1229, 2005-11-21)
pjproject-2.0-alpha2\build\os-linux.mak (284, 2007-04-18)
pjproject-2.0-alpha2\build\os-palmos.mak (898, 2005-11-21)
pjproject-2.0-alpha2\build\os-rtems.mak (462, 2006-08-21)
pjproject-2.0-alpha2\build\os-sunos.mak (287, 2006-08-21)
pjproject-2.0-alpha2\build\os-win32.mak (254, 2006-08-21)
pjproject-2.0-alpha2\build\rules.mak (4924, 2011-07-19)
pjproject-2.0-alpha2\build\vs (0, 2011-10-10)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-common-defaults.vsprops (763, 2009-04-29)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-debug-defaults.vsprops (515, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-debug-dynamic-defaults.vsprops (328, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-debug-static-defaults.vsprops (327, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-release-defaults.vsprops (416, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-release-dynamic-defaults.vsprops (332, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-release-static-defaults.vsprops (331, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-win32-common-defaults.vsprops (425, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-win32-release-defaults.vsprops (273, 2009-04-22)
pjproject-2.0-alpha2\build\vs\pjproject-vs8-wm2003-common-defaults.vsprops (843, 2009-05-07)
... ...

Copyright (C) 2003-2008 Benny Prijono Copyright (C) 2008-2011 Teluu Inc. (http://www.teluu.com) This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program. If not, see http://www.gnu.org/licenses/. Getting Started: Building and Using PJSIP and PJMEDIA [Last Update: $Date: 2007-02-02 20:42:44 +0000 (Fri, 02 Feb 2007) $] Print Friendly Page _________________________________________________________________ This article describes how to download, customize, build, and use the open source PJSIP and PJMEDIA SIP and media stack. The online (and HTML) version of this file can be downloaded from http://www.pjsip.org/using.htm Quick Info _________________________________________________________________ Building with GNU tools (Linux, *BSD, MacOS X, mingw, etc.) Generally these should be all that are needed to build the libraries, applications, and samples: $ ./configure $ make dep && make clean && make Building Win32 Target with Microsoft Visual Studio Generally we can just do these steps: 1. Visual Studio 6: open pjproject.dsw workspace, 2. Visual Studio 2005: open pjproject-vs8.sln solution, 3. Create an empty pjlib/include/pj/config_site.h, and 4. build the pjsua application. Building for Windows Mobile Generally these are all that are needed: 1. Open pjsip-apps/build/wince-evc4/wince_demos.vcw EVC4 workspace, 2. Create an empty pjlib/include/pj/config_site.h, and 3. build the pjsua_wince application. Invoking Older Build System (e.g. for RTEMS) Generally these should be all that are needed to build the libraries, applications, and samples: $ ./configure-legacy $ make dep && make clean && make Locating Output Binaries/Libraries Libraries will be put in lib directory, and binaries will be put in bin directory, under each projects. Running the Applications After successful build, you can try running pjsua application on pjsip-apps/bin directory. PJSUA manual can be found in http://www.pjsip.org/pjsua.htm page. Table of Contents: _________________________________________________________________ 1. Getting the Source Distribution 1.1 Getting the Release tarball 1.2 Getting from Subversion trunk 1.3 Source Directories Layout 2. Build Preparation 2.1 config_site.h file 2.2 Disk Space Requirements 3. Building Linux, *nix, *BSD, and MacOS X Targets with GNU Build Systems 3.1 Supported Targets 3.2 Requirements 3.3 Running configure 3.4 Running make 3.5 Cross Compilation 3.6 Build Customizations 4. Building for Windows Targets with Microsoft Visual Studio 4.1 Requirements 4.2 Building the Projects 4.3 Debugging the Sample Application 5. Building for Windows Mobile Targets (Windows CE/WinCE/PDA/SmartPhone) 5.1 Requirements 5.2 Building the Projects 6. Older PJLIB Build System for Non-Autoconf Targets (e.g. RTEMS) 6.1 Supported Targets 6.2 Invoking the Build System 7. Running the Applications 7.1 pjsua 7.2 Sample Applications 7.3 pjlib-test 7.4 pjsip-test 8. Using PJPROJECT with Applications Appendix I: Common Problems/Frequently Asked Question (FAQ) I.1 fatal error C1083: Cannot open include file: 'pj/config_site.h': No such file or directory 1. Getting the Source Code Distribution _________________________________________________________________ All libraries (PJLIB, PJLIB-UTIL, PJSIP, PJMEDIA, and PJMEDIA-CODEC) are currently distributed under a single source tree, collectively named as PJPROJECT or just PJ libraries. These libraries can be obtained by either downloading the release tarball or getting them from the Subversion trunk. 1.1 Getting the Release tarball _________________________________________________________________ Getting the released tarball is a convenient way to obtain stable version of PJPROJECT. The tarball may not contain the latest features or bug-fixes, but normally it is considered more stable as each will be tested more rigorously before released. The latest released tarball can be downloaded from the http://www.pjsip.org/download.htm. 1.2 Getting from Subversion trunk _________________________________________________________________ PJPROJECT Subversion repository will always contain the latest/most up-to-date version of the sources. Normally the Subversion repository is always kept in a "good" state. However, there's always a chance that things break and the tree doesn't build correctly (particularly for the "not-so-popular" targets), so please consult the mailing list should there be any problems. Using Subversion also has benefits of keeping the local copy of the source up to date with the main PJ source tree and to easily track the changes made to the local copy, if any. What is Subversion Subversion (SVN) is Open Source version control system similar to CVS. Subversion homepage is in http://subversion.tigris.org/ Getting Subversion Client A Subversion (SVN) client is needed to download the PJ source files from pjsip.org SVN tree. SVN client binaries can be downloaded from http://subversion.tigris.org/, and the program should be available for Windows, Linux, MacOS X, and many more platforms. Getting the Source for The First Time Once Subversion client is installed, we can use these commands to initially retrieve the latest sources from the Subversion trunk: $ svn co http://svn.pjproject.net/repos/pjproject/trunk pjproject $ cd pjproject Keeping The Local Copy Up-to-Date Once sources have been downloaded, we can keep the local copy up to date by periodically synchronizing the local source with the latest revision from the PJ's Subversion trunk. The mailing list provides best source of information about the availability of new updates in the trunk. To update the local copy with the latest changes in the main PJ's repository: $ cd pjproject $ svn update Tracking Local and Remote Changes To see what files have been changed locally: $ cd pjproject $ svn status The above command only compares local file against the original local copy, so it doesn't require Internet connection while performing the check. To see both what files have been changed locally and what files have been updated in the PJ's Subversion repository: $ cd pjproject $ svn status -u Note that this command requires active Internet connection to query the status of PJPROJECT's source repository. 1.3 Source Directories Layout _________________________________________________________________ Top-Level Directory Layout The top-level directories (denoted as $TOP here) in the source distribution contains the following sub-directories: $TOP/build Contains makefiles that are common for all projects. $TOP/pjlib Contains header and source files of PJLIB. PJLIB is the base portability and framework library which is used by all other libraries $TOP/pjlib-util Contains PJLIB-UTIL header and source files. PJLIB-UTIL is an auxiliary library that contains utility functions such as scanner, XML, STUN, MD5 algorithm, getopt() implementation, etc. $TOP/pjmedia Contains PJMEDIA and PJMEDIA-CODEC header and source files. The sources of various codecs (such as GSM, Speex, and iLBC) can be found under this directory. $TOP/pjsip Contains PJSIP header and source files. $TOP/pjsip-apps Contains source code for PJSUA and various sample applications. Individual Directory Inside Each Project Each library directory further contains these sub-directories: bin Contains binaries produced by the build process. build Contains build scripts/makefiles, project files, project workspace, etc. to build the project. In particular, it contains one Makefile file to build the project with GNU build systems, and a *.dsw workspace file to build the library with Microsoft Visual Studio 6 or later. build/output The build/output directory contains the object files and other files generated by the build process. To support building multiple targets with a single source tree, each build target will occupy a different subdirectory under this directory. build/wince-evc4 This directory contains the project/workspace files to build Windows CE/WinCE version of the project using Microsoft Embedded Visual C++ 4. build/wince-evc4/output This directory contains the library, executable, and object files generated by Windows Mobile build process. docs Contains Doxygen configuration file (doxygen.cfg) to generate online documentation from the source files. The output documentation will be put in this directory as well (for example, docs/html directory for the HTML files). (to generate Doxygen documentation from the source tree, just run "doxygen docs/doxygen.cfg" in the individual project directory. The generated files will reside in docs directory). include Contains the header files for the project. lib Contains libraries produced by the build process. src Contains the source files of the project. 2. Build Preparation _________________________________________________________________ 2.1 Create config_site.h file _________________________________________________________________ Before source files can be built, the pjlib/include/pj/config_site.h file must be created (it can just be an empty file). Note: When the Makefile based build system is used, this process is taken care by the Makefiles. But when non-Makefile based build system (such as Visual Studio) is used, the config_site.h file must be created manually. What is config_site.h File The pjlib/include/pj/config_site.h contains local customizations to the libraries. All customizations should be put in this file instead of modifying PJ's files, because if PJ's files get modified, then those modified files will not be updated the next time the source is synchronized. Or in other case, the local modification may be overwritten with the fresh copy from the SVN. Putting the local customization to the config_site.h solves this problem, because this file is not included in the version control, so it will never be overwritten by "svn update" command. Please find list of configuration macros that can be overriden from these files: * PJLIB Configuration (the pjlib/config.h file) * PJLIB-UTIL Configuration (the pjlib-util/config.h file) * PJMEDIA Configuration (the pjmedia/config.h file) * PJSIP Configuration (the pjsip/sip_config.h file) A sample config_site.h file is also available in pjlib/include/config_site_sample.h. Creating config_site.h file The simplest way is just to create an empty file, to use whetever default values set by the libraries. Another way to create the config_site.h file is to write something like the following: // Uncomment to get minimum footprint (suitable for 1-2 concurrent calls only) //#define PJ_CONFIG_MINIMAL_SIZE // Uncomment to get maximum performance //#define PJ_CONFIG_MAXIMUM_SPEED #include 2.2 Disk Space Requirements _________________________________________________________________ The building process needs: about 50-60 MB of disk space to store the uncompressed source files, and * about 30-50 MB of additional space for building each target (Visual Studio Debug and Release are considered as separate targets) 3. Building Linux, *nix, *BSD, and MacOS X Targets with GNU Build Systems _________________________________________________________________ 3.1 Supported Targets _________________________________________________________________ The new, autoconf based GNU build system can be used to build the libraries/applications for the following targets: * Linux/uC-Linux (i386, Opteron, Itanium, MIPS, PowerPC, etc.), * MacOS X (PowerPC), * mingw (i386), * FreeBSD and maybe other BSD's (i386, Opteron, etc.), * RTEMS with cross compilation (ARM, powerpc), * etc. 3.2 Requirements _________________________________________________________________ In order to use PJ's GNU build system, these typical GNU tools are needed: * GNU make (other make will not work), * GNU binutils for the target, and * GNU gcc for the target. * OpenSSL header files/libraries (optional) if TLS support is wanted. In addition, the appropriate "SDK" must be installed for the particular target (this could just be a libc and the appropriate system abstraction library such as Posix). The build system is known to work on the following hosts: * Linux, many types of distributions. * MacOS X 10.2 * mingw (Win2K, XP) * FreeBSD (must use gmake instead of make) Building Win32 applications with Cygwin is currently not supported by the autoconf script (there is some Windows header conflicts), but one can still use the old configure script by calling ./configure-legacy. More over, cross-compilations might also work with Cygwin. 3.3 Running configure _________________________________________________________________ Using Default Settings Run "./configure" without any options to let the script detect the appropriate settings for the host: $ cd pjproject $ ./configure ... Notes: The default settings build the libraries in "release" mode, with default CFLAGS set to "-O2 -DNDEBUG". To change the default CFLAGS, we can use the usual "./configure CFLAGS='-g'" construct. Features Customization With the new autoconf based build system, most configuration/customization can be specified as configure arguments. The list of customizable features can be viewed by running "./configure --help" command: $ cd pjproject $ ./configure --help ... Optional Features: --disable-floating-point Disable floating point where possible --disable-sound Exclude sound (i.e. use null sound) --disable-small-filter Exclude small filter in resampling --disable-large-filter Exclude large filter in resampling --disable-g711-plc Exclude G.711 Annex A PLC --disable-speex-aec Exclude Speex Acoustic Echo Canceller/AEC --disable-g711-codec Exclude G.711 codecs from the build --disable-l16-codec Exclude Linear/L16 codec family from the build --disable-gsm-codec Exclude GSM codec in the build --disable-speex-codec Exclude Speex codecs in the build --disable-ilbc-codec Exclude iLBC codec in the build --disable-tls Force excluding TLS support (default is autodetected based on OpenSSL availability) ... Configuring Debug Version and Other Customizations The configure script accepts standard customization, which details can be obtained by executing ./configure --help. Below is an example of specifying CFLAGS in configure: $ ./configure CFLAGS="-O3 -DNDEBUG -msoft-float -fno-builtin" ... Configuring TLS Support By default, TLS support is configured based on the availability of OpenSSL header files and libraries. If OpenSSL is available at the default include and library path locations, TLS will be enabled by the configure script. You can explicitly disable TLS support by giving the configure script --disable-tls option. 3.4 Cross Compilation _________________________________________________________________ Cross compilation should be supported, using the usual autoconf syntax: $ ./configure --host=arm-elf-linux ... Since cross-compilation is not tested as often as the "normal" build, please watch for the ./configure output for incorrect settings (well ideally this should be done for normal build too). Please refer to Porting Guide for further information about porting PJ software. 3.5 Running make _________________________________________________________________ Once the configure script completes successfully, start the build process by invoking these commands: $ cd pjproject $ make dep $ make Note: gmake may need to be specified instead of make for some hosts, to invoke GNU make instead of the native make. Description of all make targets supported by the Makefile's: all The default (or first) target to build the libraries/binaries. dep, depend Build dependencies rule from the source files. clean Clean the object files for current target, but keep the output library/binary files intact. distclean, realclean Remove all generated files (object, libraries, binaries, and dependency files) for current target. Note: make can be invoked either in the top-level PJ directory or in build directory under each project to build only the particular project. 3.6 Build Customizations _________________________________________________________________ Build features can be customized by specifying the options when running ./configure as described in Running Configure above. In addition, additional CFLAGS and LDFLAGS options can be put in user.mak file in PJ root directory (this file may need to be created if it doesn't exist). Below is a sample of user.mak file contents: export CFLAGS += -msoft-float -fno-builtin export LDFLAGS += ... ...

近期下载者：

相关文件：

评论：[我要评论] [举报此文件]

收藏者：