Changes between Initial Version and Version 1 of Getting-Started/Running-Applications


Ignore:
Timestamp:
Apr 28, 2009 5:06:13 PM (13 years ago)
Author:
ismangil
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • Getting-Started/Running-Applications

    v1 v1  
     1= Running the Applications = 
     2[[TracNav(Getting-Started/TOC)]] 
     3 
     4Upon successful build, the output libraries (PJLIB, PJLIB-UTIL, PJMEDIA, PJSIP, etc.) are put under ./lib sub-directory under each project directory. In addition, some applications may also be built, and such applications will be put in ./bin sub-directory under each project directory. 
     5 
     6  
     77.1 pjsua 
     8 
     9pjsua is the reference implementation for both PJSIP and PJMEDIA stack, and is the main target of the build system. Upon successful build, pjsua application will be put in pjsip-apps/bin directory. 
     10 
     11pjsua manual can be found in pjsua Manual Page. 
     12 
     13  
     147.2 Sample Applications 
     15 
     16Sample applications will be built with the Makefile build system. For Visual Studio, you have to build the samples manually by selecting and building the Samples project inside pjsip-apps/build/pjsip_apps.dsw project workspace. 
     17 
     18Upon successful build, the sample applications are put in pjsip-apps/bin/samples directory. 
     19 
     20The sample applications are described in PJMEDIA Samples Page and PJSIP Samples Page in the website. 
     21 
     22  
     237.3 pjlib-test 
     24 
     25pjlib-test contains comprehensive tests for testing PJLIB functionality. This application will only be built when the Makefile build system is used; with Visual Studio, one has to open pjlib.dsw project in pjlib/build directory to build this application. 
     26 
     27If you're porting PJLIB to new target, it is recommended to run this application to make sure that all functionalities works as expected. 
     28 
     29  
     307.4 pjsip-test 
     31 
     32pjsip-test contains codes for testing various SIP functionalities in PJSIP and also to benchmark static performance metrics such as message parsing per second. 
     33 
     34